Kbase P12902: How ORACLE DataServer looks for Shared Librarie libclntsh?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/15/2008 |
|
Status: Verified
GOAL:
How ORACLE DataServer looks for Shared Librarie libclntsh?
GOAL:
How the ORACLE DataServer looks for shared libraries on 32bit and 64bit platforms
GOAL:
How is the ORACLE client library libclntsh.xx, searched by the ORACLE DataServer?
GOAL:
What is ORASOPATHNAME?
GOAL:
How does Oracle dataserver look for Oracle client library?
FACT(s) (Environment):
Oracle DataServer
Progress 9.1x
Oracle 8.1.7
Oracle 9i
FIX:
Starting with 9.x, on Solaris, HPUX and True 64 platforms, Oracle dataserver dynamically accesses Oracle client library (libclntsh.xx). Starting with Version 9.1B, Progress ships 64-bit version products. ORACLE also has a 64-bit product which has either or both 32-bit and 64-bit libclntsh shipped with it.
Following is the scheme on how Progress attempts to dynamically access the ORACLE client library.
ORASOPATHNAME is a Progress environment variable that can be used to point to a particular libclntsh.so (sl).
For 32-bit platforms, Progress first checks $ORASOPATHNAME, then
$ORACLE_HOME/lib/libclntsh.so (or libclntsh.sl for hpux), then
/usr/lib/libclntsh.so (or sl).
If it's a 64-bit platform, Progress first checks $ORASOPATHNAME, then
$ORACLE_HOME/lib64/libclntsh.so (or sl) and finally /usr/lib/libclntsh.so (or sl).
The variable ORASOPATHNAME is not required to be set on either 32-bit or 64-bit platforms, unless you are using ORACLE 9i 64-bit client library on HP and Solaris.