Managing Serviceguard Extension for SAP Version B.05.10, December 2012

Set the optional parameter SQLNET.EXPIRE_TIME in sqlnet.ora to a reasonable value in order
to take advantage of the Dead Connection Detection feature of Oracle. The parameter file
sqlnet.ora resides either in /usr/sap/trans or in $ORACLE_HOME/network/admin.
The value of SQLNET.EXPIRE_TIME determines how often (in seconds) SQL*Net sends a probe
to verify that a client-server connection is still active. If the Central Instance switches, the application
servers may crash, thereby leaving shadow processes running on the database host. While the
Central Instance package cleans up the application server hosts, it does not touch the ORACLE
shadow processes running on the database host. Remove them, because their number increases
with every Central Instance package switch. After an application server crash, a connection to the
database shadow process may be left open indefinitely. If the SQLNET.EXPIRE_TIME parameter
is specified, SQL*Net sends a probe periodically to determine whether there is an invalid
connection that should be terminated. It finds the dead connections and returns an error, causing
the server process to exit.
Oracle Step: OR940
Additional steps for Oracle 9i RDBMS:
Some Oracle 9i the Oracle Installers create 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:
/sbin/init.d/init.cssdthat is linked to by /sbin/rc3.d/S<###>init.cssd
and
/sbin/rc3.d/K<###>init.cssd
Remove the following referenced links to prevent the Oracle Cluster Services Daemon from initiating
during boot time.
# rm /sbin/rc3.d/S<###>init.cssd
# rm /sbin/rc3.d/K<###>init.cssd
Database Configuration 109