Managing HP Serviceguard Extension for SAP for Linux, December 2013

In [A]SCS profile the line with Restart (number might vary)
Restart_Program_01 = local $(_EN)
has to be changed to Start.
Start_Program_01 = local $(_EN)
Avoid database startup as part of Dialog instance startup
A dialog instance installation contains Start_Program_00 = immediate $(_DB) entry in
its profile. This entry is generated by the SAP installation to start the DB before the dialog instance
is started. It is recommended to disable this entry to avoid the possible conflicts with the DB startup
managed by the SGeSAP database package.
MaxDB/liveCache: Disable Autostart of instance specific xservers
With an "isolated installation" each MaxDB/liveCache 7.8 database has its own
"installation-specific xservers". The "global xserver" exists for older databases and for forwarding
requests to the xserver of a 7.8 database.
The startup of the "global xserver" also starts the "installation-specific xserver" out of the DB specific
bin directory.
NOTE: Stopping of the global xserver does not stop the specific ones.
When running more than one 7.8 database in a clustered environment, the startup behavior can
lead to error messages (because the file system with the specific bin directory of the other DB is
not mounted) or even busy file systems error messages belonging to the other database. Therefore,
it is recommended to switch the xserver autostart feature off when running more than one
MaxDB database and or liveCache in the cluster.
However, SAP’s startDB currently relies on autostart being switched on and therefore does not
explicitly start the DB specific xserver.
Switch off the Autostart by editing the following entry:
[Params-/sapdb/<DBSID>/db] section in
/sapdb/data/config/Installations.ini:
Set XserverAutostart to no (default=yes).
A DB or liveCache SGeSAP package with the sgesap/dbinstance module or the
sgesap/livecache module configured controls the starting and stopping of the instance specific
xserver together with the package.
Oracle: Set SID specific listener names
If more than one Oracle database is configured to run on a cluster node, it is recommend to use
<SID> specific listener names to avoid conflicts. Duplicate the contents of file listener.ora.
For the first section, replace the LISTENER by LISTENER<SID1>. For the duplicated section, replace
the LISTNER with LISTENER<SID2>.
Update the HOST and PORT lines for each listener definition with the respective new values.
NOTE: If an existing package has the LISTENER name configured, then it must also be updated
with the new name. By adding tlistsrv<SID2> entries to /etc/services, the use of the port
can be documented. The ports must reflect the PORT used in listener.ora.
Check if database configuration files use the DB virtual hostname
The database installation by SAP configures the virtual host names, but it is recommended to verify
whether the Table 19 (page 68) are properly configured. You must update the files, if it is not
properly configured.
5.4 Post SAP installation tasks and final node synchronization (Phase 3a) 67