Migrating to Version 10.5 (Linux, UNIX, Windows)

Q Replication and Event Publishing Version 10.5 on Linux, UNIX, and Windows does not require a control table migration from Version 10.1.

About this task

You only need to upgrade your DB2® instance to Version 10.5, and then if required activate the replication license file. (Some editions of DB2 do not require a separate replication license.)

Q Replication and Event Publishing in Version 10.5 is functionally equivalent to Version 10.1 and there are no changes to the control tables.

CCD target tables: After you migrate Q Replication to V10.5 Fix Pack 3, the Q Apply program fails with an ASN7707E errror message because two columns in the CCD table, IBMSNAP_INTENTSEQ and IBMSNAP_COMMITSEQ, are still 10 bytes in length although the Q Capture program sends 16-byte log sequence numbers (LSN) to store in the columns. The scripts for migrating the CCD table to the longer data lengths (asnqappluwv10.sql , asnqappluwv10fp.sql ) did not include SQL statements for migrating the column lengths in the CCD table. You can install a later fix pack or follow the instructions in this Technote.

Procedure

  1. Perform the following steps on the Q Apply server:
    1. Stop the Q Apply program.
    2. Upgrade the DB2 instance to Version 10.5.
    3. Start the Q Apply program.
  2. Perform the following steps on the Q Capture server:
    1. Quiesce any applications that are updating replicated tables and let Q Capture read to the end of the DB2 log.
    2. Stop the Q Capture program.
    3. Upgrade the DB2 instance to Version 10.5.
    4. If required, activate replication by using the iidr.lic file that is included in the activation kit from InfoSphere® Data Replication Version 10.2.1.
    5. Start the Q Capture program with a startmode of warmsi or warmsn and with migrate=y.
    6. Release applications. You must start Q Capture before you release applications to avoid losing data. Q Capture cannot read any of the old logs that were created in the prior version, and it starts reading the first active log that it receives from DB2.