Adding members to a high availability disaster recovery (HADR) setup

To add a member to an HADR setup in a DB2 pureScale instance:

1. Add the new member to the standby cluster. From a standby host that is part of the DB2 pureScale instance, issue the following command:

   db2iupdt -add -m memberHostName-mnet MemberNetName -mid MemberID InstName

   This command adds the member to the member topology but not to the database topology.
2. Update the member-specific configuration parameters for the new member on the standby:

   UPDATE DATABASE CONFIGURATION FOR db_name MEMBER member_ID USING hadr_local_host standby_member_host

   UPDATE DATABASE CONFIGURATION FOR db_name MEMBER member_ID USING hadr_local_svc standby_member_port

3. Add the new member to the primary cluster. From a primary host that is part of the DB2 pureScale instance, issue the following command:

   db2iupdt -add -m memberHostName-mnet MemberNetName -mid MemberID InstName

   You must use the same member ID that you specified when adding the member to the standby cluster. This command adds the member to the member topology but not to the database topology.
4. Update the member-specific configuration parameters for the new member on the primary:

   UPDATE DATABASE CONFIGURATION FOR db_name MEMBER member_ID USING hadr_local_host primary_member_host

   UPDATE DATABASE CONFIGURATION FOR db_name MEMBER member_ID USING hadr_local_svc primary_member_port

   On the primary this member is not listed because it is not currently activated. On the standby this member is not listed because it does not yet exist in the database topology.
5. Activate the new member on the primary by doing one of the following steps:
   • Connect to the database on the new member.
   • Issue the ACTIVATE DATABASE command.
   If you have not added the member to the standby cluster by the time that it receives the add member log record that results from the member activation on the primary, the standby database will be shut down.