HP Serviceguard Enterprise Cluster Master Toolkit User Guide, June 2014

The toolkit monitor script (database instances) that continuously monitors DB2 partitions will
now stop monitoring these partitions.
The message, "DB2 toolkit pausing, monitoring, and entering maintenance mode", appears
in the Serviceguard Package Control script log for legacy packages and package configuration
log file in case of modular style of packaging.
• If required, stop the DB2 database instance:
$ cd /etc/cmcluster/pkg/db2_pkg/
$ $PWD/toolkit.sh stop
• Perform maintenance actions (For example, changing the configuration parameters in the
parameter file of the DB2 instance. If this file is changed, you must distribute the new file to
all cluster nodes).
• Start the DB2 database instance again if you have stopped it:
$ cd /etc/cmcluster/pkg/db2_pkg/
$ $PWD/toolkit.sh start
• To continue monitoring, enable monitoring scripts by removing db2.debug file:
$ rm -f /etc/cmcluster/pkg/db2_pkg/db2.debug
The message "Starting DB2 toolkit monitoring again after maintenance" appears in the
Serviceguard Package Control script log.
• Enable the package failover:
$ cmmodpkg -e db2_payroll
NOTE:
• If the package fails during maintenance (for example, the node crashes) the package does
not automatically fail over to an adoptive node. You must start the package up on an adoptive
node. For more information, see the latest Managing Serviceguard manual available at http://
www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard .
This feature is enabled only when the configuration variable MAINTENANCE_FLAG is set to
"yes" in the DB2 toolkit configuration file.
• HP suggests you to have different toolkit directories for each package. If two or more packages
share the same toolkit directory and if one package enters the maintenance mode, it will affect
the other package too.
Cluster Verification for DB2 Database Toolkit
Cluster verification is a proactive mechanism to identify cluster inconsistencies that adversely affects
toolkit package failover to a node. This mechanism checks for Serviceguard, ECMT, DB2 versions,
and supported Database Partitioning feature on all the package nodes of the cluster. If there are
any inconsistencies cluster verification displays appropriate warning messages in the standard
output.
Example:
Consider a two-node cluster, where both nodes have Serviceguard A.11.20, ECMT B.07.00.01,
or later but different DB2 versions.
To check package configuration, run the cmcheckconf command.For example: node1#
cmcheckconf -P pkg.conf
On node1, validation of the package DB2_pkg, succeeded with:
The toolkit configuration file will be backed up and a new file will be created in tkit_dir when the package
configuration is applied.
On node2, validation of package DB2_pkg succeeded with:
The toolkit configuration file will be backed up and a new file will be created in tkit_dir when the package
configuration is applied.
86 Using the DB2 Database Toolkit in a Serviceguard Cluster in HP-UX