Managing HP Serviceguard Extension for SAP for Linux, December 2013

3. Run the mv <pkg>.config<pkg>.config.SAVE command to add dbinstance module
to an existing package.
4. Run the cmmakepkg –m sgesap/dbinstance -i <pkg>.config.SAVE
<pkg>.config command
5. Edit the package configuration file to update the relevant SGeSAP attributes.
NOTE: Non SGeSAP attributes such as service or generic_resource must also be
updated.
6. Run the cmapplyconf –P <pkg>.config command to apply the configuration.
7. Run the cmrunpkg <pkg> command to start the package.
5.5.3 Module sgesap/sap_global – SAP common instance settings
This module contains the common SAP instance settings that are included by the following SGeSAP
modules:
• sapinstance
• mdminstance
• sapextinstance
• sapinfra
The following table describes the SGeSAP parameters and their respective values:
DescriptionPossible valueParameter
Defines the unique SAP System Identifier
(SAP SID)
C11sgesap/sap_global/sap_system
Defines the commands for remote
executions.
Default is ssh
ssh
rsh
sgesap/sap_global/rem_comm
Allows the parallel startup of SAP
application server instances.
If set to no, the instances start
sequentially.
yes
no
sgesap/sap_global/parallel_startup
Before the instance startups, the
package attempts to free up unused
system resources (temporary files, IPC
resources, and so on.) in order to make
the startups more likely to succeed.
A database package only frees up
database related resources. SAP
instance packages only remove IPCs
belonging to SAP administrators.
If this parameter is set to normal, only
instance shared memory is cleaned up.
If this parameter is set to lazy, cleanup
is deactivated.
If this parameter is set to strict and
process is not attached, all shared
memory - regardless of whether it is s
cleaned up.
NOTE: Using the strict setting can
crash running instances of different SAP
Systems on the failover host.
normal
lazy
strict
sgesap/sap_global/cleanup_policy
74 Clustering SAP Netweaver using SGeSAP packages