Migrating Replication Agent for UDB When DB2 is Upgraded from Version 8.2 or 9.1 to Version 9.5 or 9.7

Migrate Replication Agent for UDB when you are also upgrading DB2.

1. To prevent loss of any replicated data, deny users—other than the previously existing Replication Agent pds_username users—any further access to the primary database.
2. Log in to the Replication Agent 15.7.1 SP100 instance, verify that it is in Replicating state, and allow replication to finish. To verify that replication has completed:
   1. Periodically issue the ra_statistics command, watching until all of these statistics are 0 (zero):

      • Input queue size

      • Output queue size

   2. When all of these values are zero, note the Last QID Sent from the last set of statistics.
   3. Issue the ra_locator update command so that Replication Agent retrieves the truncation point from Replication Server.
   4. Wait, then issue the ra_locator command again and compare the displayed locator with that of the Last QID Sent. If they are different, wait and repeat this step.
   5. Quiesce the Replication Agent instance by issuing the quiesce command.
   6. Shut down the Replication instance by issuing the shutdown command.
3. Follow the steps in the DB2 documentation for upgrading DB2.
4. Verify that all the primary database requirements are met.
   Note: If the use_rssd configuration parameter was set to true before migration, skip this step.
5. Start the Replication Agent instance, and set the use_rssd configuration parameter to true:

   ra_config use_rssd, true

   Replication Agent for UDB uses this configuration to connect to the RSSD and to reset the locator to zero.

6. Migrate the Replication Agent metadata by issuing the ra_migrate command.
   
   Note: If the use_rssd configuration parameter was set to true before migration, skip this step.
7. In the Replication Agent 15.7.1 instance, resume replication by issuing the resume command.
   
8. Allow all users to access the primary database.