Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
Database Configuration
Chapter 3 171
OR920 Oracle Step:
Additional steps for Application server and Oracle 8.1.x RDBMS:
If you run an Oracle DB >= 8.1.x and install additional SAP Application
Server follow the procedure described in OSS303238 to install the
ORACLE client libraries.
If you configure multiple Application servers to be started with the
parallel startup option in sap.config, make sure the
tcp_conn_request_max ndd parameter on the DB-nodes (primary and
backup) are configured with an appropriate value:
Example: tcp_conn_request_max = 1024
If this parameter is set too low, incoming tcp connections from starting
SAP Application servers that want connect to the DB via the Oracle
Listener may halt. This will hang the starting process of the SAP
Application server.
OR940 Oracle Step:
Additional steps for Oracle 9i RDBMS:
With newer revisions of Oracle 9i the Oracle Installer creates symbolic
links in the client library directory /oracle/client/92x_64/lib that
reference to SID-specific libraries residing in the $ORACLE_HOME/lib of
that database instance. This causes trouble when the database package
is not running locally – these symbolic links can not be resolved.
Therefore these links are required to be resolved, i.e. copied locally in the
client library directory.
But only copying the client libraries locally does not solve the issue
completely: certain client libraries are linked during installation so that
the ‘shared dynamic path search’ contains the following entries (chatr
output):
LD_LIBRARY_PATH enabled first
SHLIB_PATH enabled second
embedded path enabled third /oracle/<SID>/920_64/lib
This means if the libraries are not found in LD_LIBRARY_PATH or
SHLIB_PATH, the dynamic loader again searches in the instance specific
path $ORACLE_HOME/lib. To resolve this issue, the needed libraries have
to be provided either in LD_LIBRARY_PATH or SHLIB_PATH as local copies