DB2 11 introduces changes to the DB2 catalog tables that the DB2 ECCR uses and introduces support for the extended 10-byte format of RBA and LRSN values in DB2 log records.
Before you migrate to DB2 11 conversion mode (CM), check whether the DB2 ECCR capture directory tables support DB2 11. At initialization, the ECCR issues message PWXEDM177552I, which reports the highest DB2 version that the current ECCR capture directory tables support. If the capture directory tables have already been successfully upgraded to the level required for DB2 11, the message should report that the tables support DB2 11.
If you need to upgrade the ECCR capture directory tables, perform the upgrade before migrating any subsystem to DB2 11 CM. For more information, see
Upgrading the DB2 ECCR Capture Directory Tables.
Also, check the DB2 DSN6SPRM RESTRICT_ALT_COL_FOR_DCC parameter setting. PowerExchange reports this setting in message PWXEDM177155I in the ECCR output. How this parameter is set determines whether you will need to cold start the ECCR during the migration to DB2 11 CM or enabling-new-function mode (enabling-NFM):
If the RESTRICT_ALT_COL_FOR_DCC parameter is set to NO, the ECCR will be able to process all DB2 log data that was generated during the DB2 catalog upgrade process and update the contents of the ECCR capture directory tables. If you migrate from DB2 11 CM to enabling-NFM, you must cold start the ECCR. However, if you migrate from enabling-NFM to new-function mode (NFM), you do
not
need to cold start the ECCR.
If you use this setting, shut down the DB2 ECCR before you run the DB2 catalog upgrade utility, CATMAINT.
If the RESTRICT_ALT_COL_FOR_DCC parameter is set to YES, you must cold start the ECCR after migrating to DB2 11 CM and after migrating to DB2 11 NFM.
In a data sharing environment, you might need to cold start the ECCR an additional time, depending on where the ECCR runs:
When the first member of the data sharing group is migrated to DB2 11, cold start the ECCR, regardless of whether the ECCR runs on this first-migrated member.
If the ECCR runs on another member of the data sharing group, when that member is migrated to DB2 11, cold start of the ECCR again.
If you do not cold start the ECCR in these circumstances, the ECCR will not capture any DDL changes for the tables of CDC interest. In this case, the PowerExchange capture directory tables can become invalid, causing capture processing to fail for the tables with the DDL changes.
A cold start of the ECCR is
not
required after you migrate any other member in the data sharing group.
Before you migrate a subsystem on which the ECCR will be cold started, make sure that the DB2 ECCR has captured all of the available changes from the DB2 subsystem.