Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

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.
Oracle Step: OR940
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 or symbolic links. For example
create symbolic links to these libraries in the central executable directory /sapmnt/<SID>/exe is a possible
solution.
Oracle Step: OR941
Additional steps for Oracle 10g RDBMS:
Even though no cluster services are needed when installing a Oracle 10g Single Instance, the cluster services
daemon ($ORACLE_HOME/bin/ocssd.bin) is installed. It will remain running, even when the database
is shut down. This keeps the file system busy during package shut down. Therefore it is mandatory that the
cluster services daemon is disabled.
Comment or remove the following entry in /etc/inittab:
# h1:3:respawn:/sbin/init.d/init.cssd run >/dev/null 2>&1 </dev/null
Additionally there is a init script in /sbin/init.d:
/etc/init.d/init.cssd that is linked to by /etc/rc3.d/S<###>init.cssd
and
/etc/rc3.d/K<###>init.cssd
Remove the following referenced links to prevent the Oracle Cluster Services Daemon from initiating during
boot time.
# rm /etc/rc3.d/S<###>init.cssd
# rm /etc/rc3.d/K<###>init.cssd
Additional Steps for MaxDB
Logon as root to the primary host of the database where the (db) or (dbci) package is running in debug
mode.
MaxDB Database Step: MD930
Create additional links in /sapdb/<DBSID> on the primary node.
For example:
su - sqd<sid>
ln -s .dbenv_<primary>.csh .dbenv_<secondary>.csh
ln -s .dbenv_<primary>.sh .dbenv_<secondary>.sh
exit
MaxDB Database Step: MD940
96 Step-by-Step Cluster Conversion