HP Enterprise Cluster Master Toolkit User Guide (5900-2131, December 2011)
For legacy packages, there will be 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) which
work with the three scripts mentioned above for legacy packages to integrate DB2 with the
Serviceguard Master Control Script.
Table 9 (page 76) lists these scripts:
Table 9 Legacy Package Scripts
DescriptionScript Name
This script contains a list of pre-defined variables that the user must customize
for use with a particular database instance. This is a configuration file which
hadb2.conf (user configuration file)
is read by the toolkit script, hadb2.sh. The table Table 10 (page 76) 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 will be 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 will be called 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 should 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 will be killed by sending a SIGKILL.
This variable will enable or disable maintenance mode for DB2 package. By
default, this is set to "yes". In order to disable this feature MAINTENANCE_FLAG
MAINTENANCE_FLAG
should be set to "no". When DB2 Database needs to be maintained then a
file "<package directory>/db2.debug" needs to be touched. During this
maintenance period DB2 database instance's process monitoring is paused.
Even if DB2 instance is brought down, package will not be failed over to the
standby node. To continue monitoring and come out of the maintenance mode,
you should remove the file "db2.debug" from the package configuration
directory. It is user's responsibility to ensure that db2 instance is properly
running after the maintenance phase.
NOTE: Setting MAINTENANCE_FLAG to "yes" and touching the db2.debug
file in the package directory will put the package in toolkit maintenance mode.
Serviceguard A.11.19 release has a new feature which allows 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.
76 Using the DB2 database Toolkit in a Serviceguard Cluster in HP-UX