Managing Serviceguard Extension for SAP Version A.06.00 for Linux, December 2012

During startup of the instance startup framework, a SAP instance with the SGeSAP HA library
configured , prints the following messages in the sapstartsrv.log file located at the instance
work directory:
SAP HA Trace: HP SGeSAP<versioninfo> (SG) <versioninfo> cluster-awareness
SAP HA Trace: Cluster <clustername> is up and stable
SAP HA Trace: Node <hostname> is up and running
SAP HA Trace: SAP_HA_Init returns: SAP_HA_OK ...
During startup of the instance startup framework, a SAP instance without the SGeSAP HA library
configured, prints the following message in the sapstartsrv.log file located at the instance
work directory:
No halib defined => HA support disabled
NOTE: Within a single Serviceguard package it is possible to mix instances having the HA library
configured with instances not having HA library configured.
Subsequent startup or shutdown of an instance triggers the startup framework to dynamically
discover a package that has the instance configured. A corresponding sapstartsrv.log entry
is as follows:
SAP HA Trace: Reported package name is <packagename>
During startup of the instance startup framework, a SAP instance without the SGeSAP HA library
configured prints the following message in the sapstartsrv.log file located at the instance work
directory:
No halib defined => HA support disabled
CAUTION: It might not be safe to stop an instance that has HA support disabled. Cluster software
monitors will cause a failover of the halted instance and all other software instances configured in
the same cluster package to the secondary node. You can stop the instance, if software monitoring
is not used or if package maintenance mode is activated. Ask the cluster administrator for details
on a specific configuration.
While the cluster package is running, <sid>adm can issue the following command for a SAP
instance with HA library configured:
sapcontrol -nr <instnr> -function Stop
Usually, the SAP instance shuts down as if there is no cluster configuration. The cluster package
continues to run and the filesystems remain accessible. The sapstartsrv.log file reports:
trusted unix domain socket user is stopping SAP System …
SAP HA Trace: Reported package name is ERS41SYA
SAP HA Trace: Reported resource name is SYA_ERS41
SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_OK …
SAP HA Trace: SAP_HA_StopCluster returns: SAP_HA_STOP_IN_PROGRESS
Depending on the service monitors that are configured for the instance, one or more operations
are logged to the package log file.
/var/adm/cmcluster/log/<packagename>.log in the subsequent monitoring
intervals.
<date> root@<node> sapdisp.mon[xxx]: (sapdisp.mon,check_if_stopped):
Manual start operation detected for DVEBMGS41
<date> root@<node> sapdisp.mon[xxx]: (sapdisp.mon,check_if_stopped):
Manual stop in effect for DVEBMGS41
Performing SAP administration with SAP's startup framework 23