Managing Serviceguard Extension for SAP Version B.05.10, December 2012
Copy
$ORACLE_HOME/network/admin/tnsnames.ora
to all additional application server
hosts
.
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 22 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>:
first part
( host = <relocdb_1> )
Change nothing.
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
second part
SAP system. Replace any other occurrence of <SID1> by <SID2>. The line should be modified
to contain the appropriate relocatable address belonging to the database package (db, dbci
or jdb) of the second system.
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...
108 Step-by-Step Cluster Conversion