Using the DB2 database Toolkit in a Serviceguard Cluster in HP-UX Release README: B.06.00

There might be situations, when the DB2 database has to be taken
down for
maintenance purposes like changing configuration, without having the
instance
to migrate to standby node. The following procedure should be used:
Note: The example assumes that the package name is db2_payroll,
package
directory is /etc/cmcluster/pkg/db2_pkg.
- Disable the failover of the package through cmmodpkg command.
$ cmmodpkg -d db2_payroll
- Pause the monitor script
Create an empty file /etc/cmcluster/pkg/db2_pkg/db2.debug
as shown below:
$ touch /etc/cmcluster/pkg/db2_pkg/db2.debug
Toolkit monitor script (database instances)that continuously
monitor DB2
partitions would now stop monitoring these partitions. Message,"DB2
toolkit
pausing monitoring and entering maintenance mode" appears
in the
Serviceguard Package Control script log in case of legacy packages
and log
file in the package configuration in case of modular style of
packaging.
- If required stop the DB2 database instance as shown below:
$ cd /etc/cmcluster/pkg/db2_pkg/
$ $PWD/toolkit.sh stop
- Perform maintenance actions (Example: changing the configuration
parameters
in the parameter file of the DB2 instance. If this file is changed,
please
remember to distribute the new file to all cluster nodes).
- Start the DB2 database instance again if you stopped it
$ cd /etc/cmcluster/pkg/db2_pkg/
$ $PWD/toolkit.sh start
- Enable monitoring scripts to continue monitoring by removing
db2.debug file.
$ rm -f /etc/cmcluster/pkg/db2_pkg/db2.debug