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

Table 3-3 Working with the two parts of the file
Instruction:Part of the file:
Replace each occurrence of the word LISTENER by a new listener name. You can choose what suits
your needs, but it is recommended to use the syntax LISTENER<SID1>:
( host = <relocdb_1> )
Change nothing.
first part
Replace each occurrence of the word LISTENER by a new listener name different from the one chosen
above. For example, use LISTENER<SID2> if <SID2> is the SID of the second SAP system. Replace
any other occurrence of <SID1> by <SID2>. The line should be modified to contain the appropriate
relocatible address belonging to the database package (db, or dbci) of the second system. For example:
( host = <relocdb_2> )
In the line:
( port = 1527 )
a new previously unused port should be placed. For example:
( port = 1528 )
Adapt the (host=...) and (port=...) lines corresponding to the values you have chosen in the
listener.ora file.
second part
Test your setup by starting the listeners as ora<sid1/2>:
lsnrctl start LISTENER<SID1/2>
Create a /etc/services entry for the new port you specified above. Use tlisrv<SID2> as service
name. The name is not needed anyhow. This entry has to be made on all hosts that run an instance that
belongs to the system. This includes all external application server hosts outside of the cluster.
Optional Step: OR900
If you use multiple packages for the database and SAP components:
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: OR910
Additional steps for Oracle 8.1.x RDBMS:
The sapbackup directory needs to be in $ORACLE_HOME/sapbackup. If you are using an Oracle 8.1.x
DB the $ORACLE_HOME directory is set to /oracle/<SID>/8.1.x whereas the sapbackup directory is
still placed /oracle/<SID>/sapbackup. It's best practice to create the symbolic link
$ORACLE_HOME/sapbackup -> /oracle/<SID>/sapbackup.
Oracle Step: OR920
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
Database Configuration 95