Table 12 DB2 Package Files
File Name | Description |
$PKG.cntl | Serviceguard package control script for legacy packaging style. |
$PKG.conf | Serviceguard package configuration file. |
hadb2.sh | Main shell script of the toolkit. |
hadb2.mon | Monitor the health of the application. |
hadb2.conf | Toolkit DB2 configuration file. |
toolkit.sh | Interface between pkg.cntl and hadb2.sh. |
Adding the Package to the Cluster
After the setup is complete, add the package to the SG cluster and start it up.
cmapplyconf
cmmodpkg
For more information, see Managing ServiceGuard manual available at http://www.hp.com/go/
Database Maintenance
Sometimes, 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 the cmmodpkg command: $ cmmodpkg
•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
The toolkit monitor script (database instances) that continuously monitosr DB2 partitions would now stop monitoring these partitions.
The message, "DB2 toolkit pausing, monitoring, and entering maintenance mode", appears in the Serviceguard Package Control script log in case of legacy packages and package configuration log file 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 (For example, changing the configuration parameters in the parameter file of the DB2 instance. If this file is changed, remember to distribute the new file to all cluster nodes).
•Start the DB2 database instance again if you have stopped it:
