To provide high availability only to primary database
Figure 14 HA to Primary Database
This configuration provides High Availability (HA) to primary databases. In Figure 14 (page 39), DB2 primary database is configured in a volume group shared between Node1 and Node2 in a Serviceguard cluster. The standby database is running on Node3 placed outside the cluster. The primary package is configured to run either on Node1 or Node2 and running on Node1. The standby database is not packaged using DB2 HADR toolkit.
This configuration does not provide the role management feature for DB2 HADR toolkit. Thus, the package does not handle automatic role takeover or role switch. HA to primary database is provided through failover. If primary database fails on Node1, Serviceguard brings up the primary database on Node2. The client node cannot connect to the database until it comes up on Node2. In this configuration, set the ROLE_MANAGEMENT attribute to [no].
Creating packages
To create the primary and standby package:
1.Create a directory in /etc/cmcluster, for example, /etc/cmcluster/hadr_primary.
2.Go to the /etc/cmcluster/hadr_primary directory.
3.Create the DB2 HADR packages (both primary and standby). To use two Serviceguard toolkit modules, the ECMT DB2 toolkit module and the HADR toolkit module, run the following command:
cmmakepkg –m ecmt/db2/db2 –m tkit/db2hadr/db2hadr pkg.conf
In this command,
•cmmakepkg is the Serviceguard command to create the package
•ecmt/db2/db2 is the name of the ECMT DB2 toolkit module
•tkit/db2hadr/db2hadr is the name of the DB2 HADR toolkit module
•pkg.conf is the name of the package configuration file. Edit this file and apply using the cmapplyconf command to apply the package.
Using the DB2 HADR toolkit 39