You migrate the Q Capture control tables to the Version
10.1 level after you upgrade the Q Capture server to DB2® Version 10.1 for Linux, UNIX,
and Windows.
- Stop the Q Capture program.
- Upgrade the DB2 instance
to Version 10.1. See Upgrade essentials for DB2 servers for
more information.
From this point, do not use the replication administration
tools to modify your replication configuration (for example to add
a Q subscription) until your Q Capture control tables are migrated.
- Activate InfoSphere® Data
Replication 10.1.3 by installing the InfoSphere Data Replication Activation
Kit.
- Migrate the Q Capture control tables to the Version 10.1
level:
- Find the migration script for your DB2 or Oracle source database in the sqllib/samples/repl/mig10/q/ directory.
Table 1. Migration scripts for different source databasesPlatform |
Migration script file |
DB2 |
asnqcapluwv10.sql |
Oracle |
asnoqcapluwv10.sql |
For fix pack versions: If you are
migrating to a DB2 version that includes a fix pack rather than the GA version, use the script with
a file name that includes "fp," for example asnqcapluwv10fp.sql.
- Change the variable for the Q Capture schema to your
schema.
- Change all occurrences of !CAPTABLESPACE! to
the name of the table space where your Q Capture control tables are
created.
- Run the migration script.
- Optional: Migrate any Q Apply programs that
the Q Capture program replicates to, and then ensure that the value
of the COMPATIBILITY column in the IBMQREP_CAPPARMS table is correct.
Refer to the table in Coexistence support in Version 10 for
the appropriate compatibility values. You can use the
following SQL statement to update the value:
UPDATE schema.IBMQREP_CAPPARMS
SET COMPATIBILITY = '1001';
- Start the Q Capture program with startmode=warmsi
and migrate=y.
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.