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

selections. Each Serviceguard or Serviceguard toolkit module adds one or more screens to
the dialog. Additional information on the SGeSAP specific screens are described below.
GI020 Select the SAP system that is to be clustered (sgesap/sap_global module)
Most SGeSAP packages are associated with a single SAP system. There is a dialog screen that
allows to select that system as well as a couple of package configuration settings that have impact
on all SGeSAP modules in the package.
1. In many situations, Serviceguard Manager Auto-Discovery can discover the SAP systems in
the cluster. If Serviceguard Manager can discover the SAP systems, you can select a SAP
system ID from a drop-down list. It is always possible to enter one manually.
2. Many SGeSAP package activities depend on system resources that are provided via
mechanisms that are not directly handled by the package. If these resources are not available,
a package operation could fail. Sometimes the resources are just temporarily unavailable and
the package activity would succeed if delayed long enough. To allow that kind of
synchronization, SGeSAP enters loops that poll missing resources regularly and delays or
retries activities that depend on these resources. The package activity continues after the
resource becomes available again or fails after the maximum number of attempts specified
in the field Retry Count.
The default for the parameter is set to 5. It should be raised on demand, if the package logs
indicate racing conditions with timing issues.
3. The remote communication value defines the method to be used to remotely execute commands
for SAP Application Server handling. Setting the parameter is optional. It can be set to ssh
to rely on secure encrypted communications between untrusted hosts over an insecure network.
For information on how to set up ssh for each node, refer to “Section Cluster Node
Configuration.” Default value is remsh.
4. The following influences the system cleanup behavior of SGeSAP.
Prior to any instance startup attempts the SGeSAP tries to free up unused or unimportant
resources to make the startup more likely to succeed. A database package only frees up
database related resources, a SAP Instance package only removes IPCs belonging to SAP
administrators. The following list summarizes how the behavior of SGeSAP is affected with
different settings of the Cleanup Policy parameter:
• lazy—no action, no cleanup of resources.
• normal—removes orphaned resources as reported by SAP tools for SAP system. An
obsolete ORACLE SGA is also removed if a database crash occurred.
• strict—uses HP-UX commands to free up system resources that belong to any SAP
Instance of any SAP system on the host if the Instance is to be started soon.
NOTE: Do not use the strict policy unless it is required. Be aware that the strict option can
crash running instances of different SAP systems on the backup host. Use this value only if you
have a productive system that is much more important than any other SAP system you have.
In this case a switchover of the productive system is more robust, but additional SAP systems
will crash.
You can also use strict policy, if your SAP system is the only one running at the site and you
are low on memory. Strict policy frees up more of its own shared memory segments than the
normal policy does.
GI030 Select the SAP instances that are to be clustered (sgesap/sapinstance module)
It is possible to put several SAP instances into one package. The agent of the SAP startup framework
that belong to the instance is handled automatically. For SAP releases based on kernel 7.10 or
higher, SGeSAP registers an instance with the startup framework as part of the package startup
operation and unregisters it as part of the package halt. If the service agent is started via SGeSAP
74 Step-by-Step Cluster Conversion