Managing Serviceguard Extension for SAP Version B.05.10, December 2012

continues to run. Make sure that the packaged SAP instance is already running when removing
the debug file or an immediate failover will occur. As long as the debug file exists locally, a
package shutdown would not try to stop the SAP instance or its database. A local restart of the
package would only take care of the HA NFS portion. The instance would not be started with the
package and the monitor would be started in paused mode.
Example entries in <pkg_name>.config:
Message Server Monitor:
SERVICE_NAME ciC11ms
SERVICE_FAIL_FAST_ENABLED YES
SERVICE_HALT_TIMEOUT 300
Dispatcher Monitor:
SERVICE_NAME ciC11disp
SERVICE_FAIL_FAST_ENABLED YES
SERVICE_HALT_TIMEOUT 300
The service name and command referencing the SAP message server monitor and SAP dispatcher
monitor must be specified in <pkg_name>.control.script to use the service defined in the
config files <pkg_name>.config. If no configuration parameters are provided with the service
command, the monitors will default to the settings for a ABAP DVEBMGS Central Instance if possible.
Example entries in <pkg_name>.control.script:
SEVICE_NAME[0]="ciC11ms"
SERVICE_CMD[0]="/etc/cmcluster/C11/sapms.mon <MS_SERVICEPORT>"
SEVICE_NAME[1]="ciC11disp"
SERVICE_CMD[1]="/etc/cmcluster/C11/sapdisp.mon <INSTNAME> <INSTNR> <hostname>"
Optional Step: OS445
In case you want to automate Replicated Enqueue handling and use follow-and-push failover
semantics for[A]SCS/[A]REP packages:
For this to work with legacy packages, section 1 of the SGeSAP configuration file needs to reside
in the file /etc/cmcluster/<SID>/sap.config. This is the default approach even without
the follow-and-push and it can always be done, also if several SGeSAP packages share this package
directory. Other sections of the file can be moved to package the specific file.
/etc/cmcluster/<SID>/sap<packagename>.config if required.
The SGeSAP ENQueue Operation Resource needs to be specified for each [A]SCS package and
for each [A]REP replication package in the package configuration files.
Example entries for a ASCS package configuration file:
RESOURCE_NAME /applications/sap/enqor/C11ascs
RESOURCE_POLLING_INTERVAL 30
RESOURCE_START AUTOMATIC
RESOURCE_UP_VALUE != "IDLE"
Example entries for an AREP package configuration file:
RESOURCE_NAME /applications/sap/enqor/C11ascs
RESOURCE_POLLING_INTERVAL 60
RESOURCE_START AUTOMATIC
RESOURCE_UP_VALUE != "SERVING"
You will need to copy /opt/cmcluster/sap/sap.config to /etc/cmcluster if you use
non-default package names. Default package names for setups with Replicated Enqueue are
ascs<SID>, scs<SID>, and ers<INR><SID>. Within the file, any non-default names have to
be specified explicitly. If these values have to be changed during operation, the cmenqord process
needs to be notified by sending it the signal USR1 via the kill command.
For SAP kernel 4.6 or 6.x and resources
/applications/sap/enqor/<SID>
/applications/sap/enqor/<SID>scs
use:
90 Step-by-Step Cluster Conversion