Managing Serviceguard Extension for SAP, December 2007

SGeSAP Cluster Administration
Switching SGeSAP Off and On
Chapter 6 315
Switching On SGeSAP
Perform the following steps to switch SGeSAP on again.
SO500: Switch on step:
Stop the database and SAP instances manually on all hosts in and
outside of the cluster with:
stopsap all
SO510: Switch on step:
Restore all profiles with the versions that use relocatable addresses.
They were backed up in step SO040. If appropriate, incorporate any
changes that occurred to these files during the switch off process. You
can use diff(1) and the second backup you took in SO080 to easily find
out if anything changed.
SO520: Switch on step (Informix database only):
As informix user perform the following from your home directory:
rm /informix/<SID>/etc/onconfig.<local_hostname>.<DBID>
mv .customer.csh.off .customer.sh
mv .customer.csh.off .customer.csh
As <sid>adm in home directory:
mv .customer.csh.off .customer.sh
mv .customer.csh.off .customer.csh
SO530: Switch on step:
Delete /etc/cmcluster/debug and/or /etc/cmcluster/<SID>/debug
if they exist.
SO540: Switch on step:
• The SAP software needs to be reconfigured.
• Import the profiles within a SAP session. Transaction code: RZ10.
• Check SAP setup. Try to ping(1M) to all application servers from the
Central Instance and the other way round. Transaction code: SM59.
• Check that the batch jobs in SAP are scheduled to run on the
relocatable IP address not on the local hostname. Transaction code:
SM36