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

database clients reconnect to this database using the Automatic Client Reroute feature of DB2
HADR.
If the ROLE_MANAGEMENT attribute is set to [no], behavior is the same as in Event 2.
Event 4: Primary package is manually halted
If the primary package is halted using the cmhaltpkg command, the standby package does not
perform a role takeover. The standby package continues to run and logs a message in the package
log stating that the primary package is manually halted. There is no other impact on the standby
package when the primary package is halted manually.
Event 5: The failed primary package restarts on the primary node
This scenario is a continuation of Event 3 and 4. After the initial role takeover, the original primary
package attempts to start as the primary package. The primary package fails to come up as the
primary package because a role takeover was performed when the primary package went down,
and the original standby package is now running as primary HADR. In this case the package
attempts to come up as standby. However, if it fails to come up as standby, it halts the package
but if it is successful, it performs the following tasks:
1. Syncs up with the primary HADR and retrieves all the pending DB2 database archive logs.
This is a HADR feature and toolkit does not perform this task.
2. After the logs are in sync, the HADR on both nodes move to the Peer state.
3. If the RESTORE_ROLE package attribute is set to [yes], the original primary package performs
a role switch to resume its role as the primary database. This automatically enables the original
standby database to resume as the standby database.
4. If the RESTORE_ROLE package attribute is set to [no], the original primary (which is now
standby), continues to run as standby.
When primary and standby packages are in different clusters
Figure 13 Primary and Standby Packages in Different Clusters
In this configuration, Figure 13 (page 38), SG Cluster1 and SG Cluster 2 are configured for the
primary and standby package, respectively. Node1 and Node2 shares the volume group on which
the primary database is configured. Primary package can run on both the nodes. Similarly, the
standby database is configured on the volume group that is shared between Node3 and Node4.
Standby package can run on both the nodes.
NOTE: For more information on events, see When primary and standby packages are in the
same cluster.
To provide high availability only to primary database
38 Serviceguard toolkit for DB2 High Availability Disaster Recovery