Enterprise Cluster Master Toolkit User Guide April 2011 (5900-1606)

nodes that will be configured to run this database instance. Since the volume group and file
system have to be uniquely named within the cluster, use the name of the database instance
in the name. Assuming, the name of the database instance is 'payroll_inst', follow the
instructions in the see Building an HA Cluster Configuration chapter of 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
After waiting for a few minutes, check for the existence of DB2 processes (there should be
several, identified by "db2") ps -ef | grep db2. Bring the database down, unmount, and
deactivate the volume group.
./toolkit.sh stop
umount /mnt/payroll
vgchange -a n /dev/vg0_payroll
Repeat this step on all other clustered nodes to be configured to run the package to ensure
DB2 can be brought up and down successfully.
78 Using the DB2 database Toolkit in a Serviceguard Cluster in HP-UX