HP Serviceguard Toolkits for Database Replication Solutions User Guide, March 2012

1. To enable the maintenance mode, in the Package Configuration file, set the
MAINTENANCE_FLAG attribute to [Yes ] before applying the cmapplyconf command.
2. To start the maintenance mode for the HADR package in the TKIT_DIR of HADR package,,
create the hadr.debug file.
NOTE:
• If you set the dependent ECMT DB2 package in the maintenance mode (create db2.debug
file in the TKIT_DIR of the ECMT DB2 package), the HADR package automatically goes
to the maintenance mode, because the HADR package is dependent on the ECMT DB2
package.
• If the ECMT DB2 package fails, the dependent HADR packages also fail, even if it is in
the maintenance mode. This is because of the Serviceguard behavior, that is, when a
package on which other packages depend, fails, all the dependent packages also fail.
For more information on how to set the ECMT DB2 package in the maintenance mode, see
the latest HP Serviceguard Enterprise Cluster Master Toolkit User Guide manual at
www.hp.com/go/hpux-serviceguard-docs → HP Serviceguard Enterprise Cluster Master
Toolkit.
3. To stop the maintenance mode and bring the package back to the running state, remove the
hadr.debug file from the TKIT_DIR directory of the HADR package.
If you stop maintenance for the dependent ECMT DB2 package (that is, remove the db2.debug
file from the TKIT_DIR of the ECMT DB2 package), the HADR package also stops the
maintenance mode.
Halting packages
To halt a package, run the following command:
# cmhaltpkg <package_name>
NOTE:
• It is recommended to stop the primary package before stopping the standby package. This
ensures that the standby database is in sync with the primary database.
• If you have used the separate packaging method to create a package, halt the dependent
HADR packages before you halt the corresponding ECMT DB2 package.
Cluster verification for DB2 HADR toolkit
Cluster verification is a proactive mechanism to identify the cluster inconsistencies that adversely
affect the toolkit package failover to a node. This mechanism checks for Serviceguard supported
DB2 versions and HP Serviceguard Toolkits for Database Replication Solutions version on all the
package nodes of a cluster. Cluster verification is supported in Serviceguard A.11.20 and HP
Serviceguard Toolkits for Database Replication Solutions B.02.00 or later. If there are any
inconsistencies, the cmcheckconf command does not fail, but logs appropriate warning messages.
For example:
Consider a two-node cluster, where both nodes have Serviceguard A.11.20, but different versions
of HP Serviceguard Toolkits for Database Replication Solutions.
To check the package configuration, run the cmcheckconf command.
For example: node1# cmcheckconf -P pkg.conf
On node1, validation of the package HADR_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 HADR_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.
WARNING: Unsupported DB2 version on package nodes. Refer Support Matrix.
Cluster verification for DB2 HADR toolkit 49