Updating the CDC Replication bookmark format for Db2 Database version 9.7

You must follow a number of steps before you start the upgrade of your replicated database to Db2® Database version 9.7.

About this task

Note: The following procedure is not required if you have already installed CDC Replication version 6.3 Fix Pack 2.

Before starting the upgrade of your replicated database to Db2 Database version 9.7, you must do the following:

  • Ensure that all of your subscriptions have applied all data to the target. There should be no latency. All data that is not applied to the target will be lost as a result of this upgrade.
  • Do not stop and start or make changes in your Db2 LUW database during the following upgrade process. Db2 Database moves the bookmark forward each time and there is the risk of losing changed data when you upgrade CDC Replication.

Procedure

  1. Quiesce the database using the Db2 LUW QUIESCE DB command. For more information, see Ending replication / quiescing the database.

    This action prevents all users from making any changes to the tables in the source database. Subsequently, verify that all subscriptions have replicated any pending changes to the target and have successfully committed them. In other words, confirm that all subscriptions have reached Head Of Log (HOL) with zero latency. This step ensures that the CDC Replication Engine for Db2 Database finishes reading and applying all changes in the logs after users stop updating the Db2 LUW database.

  2. Stop the database and the CDC Replication Engine for Db2 Database instance.
  3. Upgrade your Db2 Database database to version 12.x.

    For more information, see your IBM® Db2 LUW database documentation.

  4. Ensure that you have adjusted your classpath and library path values to reflect your new database version number. For more information, see Adjusting classpath and library path values after database upgrades.
  5. Start all of your CDC Replication instances.
  6. Mark the capture point for all tables by using the CDC Mark Table Capture Point command. For more information, see Marking a table capture point on a source table before mirroring.
  7. Run the DB2 LUW UNQUIESCE DB command to allow users to resume making changes to the source tables.

What to do next

The upgrade process is now complete and you can start replication.