Migrating to replication and publishing Version 9.7 Fix Pack 3 or 3a (Linux, UNIX, Windows)

Migrating the Q Apply server first

Follow these steps to migrate the Q Apply server first. You can use this procedure with a single Q Capture program that replicates to a single Q Apply program or to multiple Q Apply programs.

1. Optional: Stop the Replication Alert Monitor to prevent the monitor from issuing alerts while the replication programs are stopped for migration.
2. Stop the Q Apply program.
   Note: If your Q Capture program is processing a high volume of data, the receive queue could fill while Q Apply is stopped, prompting the source transmission queue to fill and Q Capture to stop. If this happens, you can start Q Capture after Q Apply migration is complete and Q Apply then starts processing messages on the receive queue.
3. Migrate the DB2 instance to Version 9.7 Fix Pack 3 or 3a by running the fix pack installer, which also upgrades the Q Apply server to Version 9.7 Fix Pack 3 or 3a.

   From this point, do not use the replication administration tools to modify your configuration (for example, add a Q subscription) until the Q Apply control tables are migrated.

4. Migrate the control tables:
   1. Find the Q Apply migration script for your DB2 or federated target in the sqllib/samples/repl/mig97/q/ directory:

      Platform	Migration script file
      DB2	asnqappluwv97fp.sql
      Informix	asnqappinfxv97fp.sql
      Oracle	asnqapporav97fp.sql
      Microsoft SQL Server	asnqappmssqlv97fp.sql

   2. Delete or comment out statements that apply to fix packs other than Version 9.7 Fix Pack 3 or 3a.
   3. In the remainder of the script, replace the schema and table space names as required and run the script.
5. You can now start the Version 9.7 Fix Pack 3 or 3a Q Apply program to work with your Q Capture program.

If you are ready to migrate the Q Capture server next, follow these steps:

1. If you are migrating from Version 9.5 or earlier, quiesce all applications on the Q Capture server and let Q Capture read to the end of the DB2 log. This action ensures that no pre-Version 9.7 log records are generated that cannot be read by the V9.7 DB2 or Q Capture.
2. Stop the Q Capture program.
3. Migrate the DB2 instance to Version 9.7 Fix Pack 3 or 3a by running the fix pack installer, which also upgrades the Q Capture server to Version 9.7 Fix Pack 3 or 3a.

   From this point, do not use replication administration to modify your replication configuration (for example to add a Q subscription) until your Q Capture control tables are migrated.

4. Migrate the control tables:
   1. Find the asnqcapluwv97fp.sql migration script in the sqllib/samples/repl/mig97/q/ directory.
   2. Delete or comment out statements that apply to fix packs other than Version 9.7 Fix Pack 3 or 3a.
   3. Change all occurrences of !capschema! to your Q Capture schema.
   4. Change all occurrences of !qcsubbp! and !qcsubts! to the name of the buffer pool and table space where you want the IBMQREP_SUBS table to be created. You must create the IBMQREP_SUBS table in a table space with 8K page size.
   5. Run the script.
5. If all of the Q Apply programs that this Q Capture program replicates to are migrated to Version 9.7 Fix Pack 3 or 3a, change the value of the COMPATIBILITY column in the IBMQREP_CAPPARMS table to 0907. Use the following SQL statement:

   UPDATE schema.IBMQREP_CAPPARMS
   SET COMPATIBILITY = '0907';

6. Reorganize the following control tables whose column data types or lengths were changed by the migration:
   • IBMQREP_CAPMON
   • IBMQREP_CAPQMON
   • IBMQREP_APPLYMON
   • IBMQREP_IGNTRANTRC
   • IBMQREP_SIGNAL
7. Start the Version 9.7 Fix Pack 3 or 3a Q Capture program with the parameters migrate=y and startmode=warmns.
   Recommendation: Start the Q Capture program as soon as possible after the migration, before you start other applications if possible. DB2 provides replication with the first valid log sequence number (LSN) within the current set of active log files as determined by the LOGPRIMARY database parameter. You should start Q Capture soon enough to ensure that all of the transactions that need to be captured can be found in the active log files.
8. Start the Replication Alert Monitor if you stopped it.

Migrating the Q Capture server before migrating multiple Q Apply servers

This procedure is a slight modification of the above procedures for use with multiple Q Capture or Q Apply servers.

1. Follow the steps above for migrating a Q Capture server.
2. Start the Version 9.7 Fix Pack 3 or 3a Q Capture program.
3. If you have more than one Q Capture program, migrate each one. Q Capture programs do not have to be migrated all at once.
4. Follow the steps above to migrate a Q Apply program.
5. You can now start the Version 9.7 Fix Pack 3 or 3a Q Apply program to work with your Version 9.7 Fix Pack 3 or 3a Q Capture program.
6. Repeat the migration steps for each Q Apply program that you want to migrate.