HP Serviceguard Enterprise Cluster Master Toolkit User Guide, December 2012 (5900-2145)

For legacy packages, there is one user configuration script (hadb2.conf) and three functional
scripts (toolkit.sh, hadb2.sh, and hadb2.mon) which work with each other to integrate
DB2 with the Serviceguard package control scripts.
For modular packages, there is an Attribute Definition File (ADF), a Toolkit Module Script
(tkit_module.sh), and a Toolkit Configuration File Generator Script (tkit_gen.sh) that work
with the three scripts (toolkit.sh, hadb2.sh and hadb2.mon) for legacy packages to integrate DB2
with the Serviceguard Master Control Script.
Table 9 (page 79) lists these the scripts:
Table 9 Legacy Package Scripts
DescriptionScript Name
This script contains a list of pre-defined variables that you must customize for
use with a particular database instance. This is a configuration file which is
hadb2.conf (user configuration file)
read by the toolkit script, hadb2.sh. The table Table 10 (page 79) shows
variables that are contained in hadb2.conf.
This script contains a list of internally used variables and functions that support
starting and stopping of a DB2 database instance. This script is called by
toolkit.sh to perform the following:
Main Script (hadb2.sh)
• On package startup, it starts the DB2 instance and monitor process.
• On package halt, it stops the DB2 instance and monitor process.
This script contains a list of internally used variables and functions for
monitoring a DB2 server instance. This script iscalled by hadb2.sh . It uses a
tool called "db2gcf" to monitor the database.
Monitor Script (hadb2.mon)
This script is the interface between the Serviceguard package control script
and the DB2 toolkit.
Interface Script (toolkit.sh)
Table 10 Variables in hadb2.conf File
DescriptionVariable Name
The DB2 instance name.INSTANCE_NAME
The list of the logical database partitions that participate in a DB2 instance
and are intended to run on single server. Physical partitions must be packaged
separately.
PARTITION_NUMBER
This is the list of critical processes of a DB2 instance.MONITOR_PROCESSES
NOTE: These processes must not be running after DB2 is shutdown. If the
processes are still running they are killed by sending a SIGKILL.
This variable will enables or disables maintenance mode for DB2 package.
By default, this is set to "yes". To disable this feature MAINTENANCE_FLAG
MAINTENANCE_FLAG
must be set to "no". When DB2 Database needs maintenance, a file
"<package directory>/db2.debug" must be created. During this maintenance
period process monitoring for DB2 database instance is paused. Even if DB2
instance is brought down, the package does not failover to the standby node.
To continue monitoring and come out of the maintenance mode, you must
remove the file "db2.debug" from the package configuration directory. You
must ensure that db2 instance is properly running after the maintenance phase.
NOTE: If you setMAINTENANCE_FLAG to "yes" and touch the db2.debug
file in the package directory, the package in the toolkit moves into maintenance
mode. Serviceguard A.11.19 release includes a new feature which enables
individual components of the package to be maintained while the package
is still up. This feature is called Package Maintenance mode and is available
only for modular packages. For more information on using Package
Maintenance mode, see the whitepaper "Modular package support in
Serviceguard for Linux and ECM Toolkits" available at http://www.hp.com/
go/hpux-SG-ECMT-docs.
Setting up the Toolkit 79