HP Serviceguard Extension for SAP (SGeSAP) manual Lsnrctl start LISTENERSID1/2

Be careful if these files were customized after the SAP installation.

Oracle Database Step: OR880

Be sure to configure and install the required Oracle NLS files and client libraries as mentioned in section Oracle Storage Considerations included in chapter Planning the Storage Layout.

Also refer to SAP OSS Note 180430 for more details.

Optional Step: OR890

If you use more than one SAP system inside of your cluster...

It is possible that more than one database is running on the same node. Even though one listener is capable of serving many database instances problems can occur in switchover environments because needed file systems may not be available at the startup time of the listener. Use a dedicated listener process for each database.

You can use the standard file that is created during the installation of one SAP system <SID1> as a template. Double its contents, for example:

cat listener.ora listener.ora >listener.ora.new

mv listener.ora.new listener.ora

The file consists of two identical parts

Table 3-8 Working with the two parts of the file

Part of the file:	Instruction:
first part	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.
second 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, dbci or jdb) 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.

Test your setup by starting the listeners as ora<sid1/2>:

lsnrctl start LISTENER<SID1/2>

Create an /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

Database Configuration 85