Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion

Cluster Configuration

Chapter 3 141

NOTE The manual startup using common startsap/stopsap scripts may not

work correctly with Netweaver 2004s based Application Servers. In this

case the instances need to started by directly using the sapstart binary

passing the start profile as a parameter. For example:

sapstart pf=/sapmnt/<SID>/profile/START_\

The service monitor will not be able to detect a stopsap command and

will consider a manual instance shutdown to be a failure. The package

will then fail over the instance to another node. The existence of the

debug file can prevent that. If the debug file gets removed, the service

monitor 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 in order 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: