Attributes | Description |
| For DB2 HADR Service |
service_name | Name of the service that Serviceguard monitors while |
| the package is up. This name must be unique for both |
| primary and standby packages in a Serviceguard |
| cluster. The default value is db2hadr_service. |
service_cmd | $SGCONF/scripts/tkit/db2hadr/ |
| tkit_module.sh db2hadr_monitor |
service_restart | This attribute specifies the number of times the service |
| was restarted before failing. The default value is [none]. |
service_fail_fast_enabled | This attribute enables Serviceguard to halt the node if |
| the service fails on that node. The default value is set to |
| [no]. |
service_halt_timeout | It is used to determine the duration for which |
| Serviceguard waits for the service to halt before a |
| SIGKILL signal. The default value is [300 seconds]. |
5.After the package configuration file is edited, save the file.
6.To validate the package configuration file, run the command: cmcheckconf
7.To apply the command if the cmcheckconf command succeeds, run the command: cmapplyconf
8.Confirm if you want to modify the package configuration. The default value is [yes]
9.To enable auto run and package failover, run the following commands, $ cmmodpkg
and, $ cmmodpkg -e hadrpkg
10.To verify that the package is created, run the cmviewcl command.
Managing packages
Running packages
To start the DB2 database and DB2 HADR, start the package using the following command:
# cmrunpkg <package_name>.
NOTE:
•The start command is the same for both primary and standby packages.
•You must start the standby package before starting the primary package. Otherwise, the primary package fails to start.
Maintaining packages
When packages are set to the maintenance mode, it handles the maintenance work on both DB2 database and DB2 HADR without bringing down the package.
Perform the following steps to work with the package maintenance mode:
42 Serviceguard toolkit for DB2 High Availability Disaster Recovery
