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

Step-by-Step Cluster Conversion
Cluster Configuration
Chapter 3138
Serviceguard Control Script Template - xxx.control.script
IS470 Installation Step:
The script that get executed for “running” or “halting” a Serviceguard
package is the Serviceguard control script (xxx.control.script). It is
located in directory ${SGCONF}/<SID>.
In xxx.control.script the volume groups, logical volumes, the virtual
IP addresses and subnets and last not least the SGeSAP/LX scripts to
run and halt SAP instances are added.
The following is an extract of two (db) db.control.script files: the first one
for an Oracle configuration, the second one for a MaxDB configuration.
The customer_defined_run_commands and the
customer_defined_halt_commands enable the SAP specific scripts.
The following is an extract of a (db) package based on Oracle for SAP
instance XI7 in directory ${SGCONF}/XI7/db.control.script:
# VOLUME GROUPS
# #Specify which volume groups are used by this package. Uncomment VG[0]=""
# and fill in the name of your first volume group. You must begin with
# VG[0], and increment the list in sequence.
#
# For example, if this package uses your volume groups vg01 and vg02, enter:
# VG[0]=vg01
# VG[1]=vg02
#
VG[0]="vgC11_oracleC11"
# FILESYSTEMS
# The filesystems are defined as entries specifying the logical
# volume, the mount point, the file system type, the mount,
# umount and fsck options.
# Each filesystem will be fsck'd prior to being mounted.
# The filesystems will be mounted in the order specified during package
# startup and will be unmounted in reverse order during package
# shutdown. Ensure that volume groups referenced by the logical volume