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

Table 10 Variables in hadb2.conf File (continued)
DescriptionVariable Name
The time interval in seconds between the checks to ensure that the DB2
database is running. Default value is 30 seconds.
MONITOR_INTERVAL
The amount of time, in seconds, to wait for the DB2 shutdown to complete
before killing the DB2 processes defined in MONITOR_PROCESSES. The
TIME_OUT
TIME_OUT variable is used to protect against a worst case scenario where a
hung database prevents the package halt script from completing, thereby
preventing the standby node from starting the database. The value of
TIME_OUT must be less than the HALT_SCRIPT_TIMEOUT value set in the
package configuration file. This variable has no effect on the package failover
times.
The following ADF file and scripts are used only during the modular method of packaging.
Table 11 Modular Package Scripts
DescriptionScript Name
For every parameter, in the legacy toolkit user configuration file, there is an
attribute in the ADF. It also has an additional attribute TKIT_DIR which is
Attribute Definition File (db2)
analogous to the package directory in the legacy method of packaging. The
ADF is used to generate the package ASCII template file.
This script is called by the Master Control Script and acts as an interface
between the Master Control Script and the Toolkit interface script (toolkit.sh).
It is responsible for calling the Toolkit Configuration File Generator Script.
Module Script (tkit_module.sh)
This script is called by the Module Script when the package configuration is
applied using cmapplyconf command to generate the toolkit user
configuration file in the package directory (TKIT_DIR).
Toolkit Configuration File Generator
Script (tkit_gen.sh)
DB2 Package configuration example
Configuring the package when DB2 is already installed
1. To create a logical volume infrastructure on a shared disk, see Building an HA Cluster
Configuration chapter of Managing Serviceguard manual available at http://www.hp.com/
go/hpux-serviceguard-docs —>HP Serviceguard . The disk must be exposed to all clustered
nodes that are configured to run this database instance. The volume group and file system
have to be uniquely named within the cluster, use the name of the database instance in the
name. Consider that the name of the database instance is 'payroll_inst', for more information,
see theBuilding an HA Cluster Configuration in the latest Managing Serviceguard manual
available at http://www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard to create
the following:
/dev/vg0_payroll (the volume group)
/dev/vg0_payroll/lvol1 (the logical volume)
/dev/vg0_payroll/lvol1 (the filesystem) mounted at /mnt/payroll
2. Test the set up to ensure that DB2 can be properly brought up. Tert st DB2 to ensure that it
can be properly started by executing the script toolkit.sh.
For example:
cd /tmp/db2
cp /opt/cmcluster/toolkit/db2/* .
Edit the DB2 toolkit configuration file hadb2.conf
./toolkit.sh start
80 Using the DB2 Database Toolkit in a Serviceguard Cluster in HP-UX