Precompilers and OCI (MOSC)

MOSC Banner

32-bit 'C' application moving from oracle 11.2 client libraries to oracle 19c client libraries

in Precompilers and OCI (MOSC) 1 commentAnswered

32-bit oracle client libraries for 'C' OCI application on Red Hat Linux

Currently we have a 32-bit 'C' application component running on RHEL 7.9 and using the 32-bit oracle 11.2 client libraries. This component uses the following ORACLE_HOME:

/tools/ver/oracle-11.2.0.3-32/client

and the compiled application component is dependent at runtime on the following 2 libraries:

libclntsh.so.11.1 => /tools/ver/oracle-11.2.0.3-32/client/lib/libclntsh.so.11.1 (0xf511e000)

libnnz11.so => /tools/ver/oracle-11.2.0.3-32/client/lib/libnnz11.so (0xf4344000)

My hope is to install the oracle 19c client under /tools/ver/oracle-19.x.x.x-32. Then I would rename the two oracle 11.2 libraries above (libclntsh.so.11.1 and libnnz11.so) and in their place create links using the original names. The new links would point to the same library under the oracle 19c install directory. Then at runtime I will have the 32-bit 'C' application set ORACLE_HOME to the following:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center