Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
Serviceguard Extension for SAP on Linux Configuration – sap.config
Chapter 3158
can significantly speed up the package start and stop, especially if
Windows NT application servers are used. Use this value only if you
have carefully tested and verified that timing issues will not occur.
OS710 Optional Step:
Specify SAPOSCOL_STOP=1 if saposcol should be stopped together with
each instance that is stopped. The collector will only be stopped if there
is no instance of an SAP system running on the host. Specify
SAPOSCOL_START=1 to start the saposcol even with packages that don't
use the implicit startup mechanism that comes with SAP instance
startup, e.g. database-only packages or packages that only have a SCS,
ASCS or AREP instance.
OS720 Optional Step:
If several packages start on a single node after a failover, it is likely that
some packages start up faster than others on which they might depend.
To allow synchronization in this case, there is a loop implemented that
polls the missing resources regularly.
After the first poll, the script will wait 5 seconds before initiating the
next polling attempt. The polling interval is doubled after each attempt
with an upper limit of 30 seconds. Polling continues until the resource
becomes available or up to a maximum of DELAY_INTERVALS polling
attempts.
OS730 Optional Step:
Control the handling of resources.
On Linux, a shared memory shortage can occur if you install more than
one instance on a host. Prior to any instance startup the Serviceguard
Extension for SAP on Linux 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 Central Instance
package only removes IPCs belonging to SAP administrators.
The following list summarizes how the behavior of Serviceguard
Extension for SAP on Linux is affected by changing the CLEANUP_POLICY
parameter:
• lazy – no action, no cleanup of resources
• normal – removes unused resources belonging to the own system