CDC Guide for z/OS

10.5.1
- 10.5.8
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

If You Migrate to DB2 12 for z/OS

If you plan to migrate to DB2 12 for z/OS from an earlier DB2 version, you do not need to upgrade the DB2 ECCR capture directory tables. No changes have been made to the structure of these tables since DB2 11.

At initialization, the DB2 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 12, the message should report that the tables support DB2 12.

Before you migrate, 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 DB2 migration, as follows:

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. A cold start is not required.

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, the first time you start the ECCR after migrating to DB2 12.1.100, you must perform a cold start. In a data sharing environment, you might need to cold start the ECCR an additional time, depending on where it runs:

When the first member of the data sharing group is migrated to DB2 12.1.100, 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 12.1.100, 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.

When you upgrade from DB2 12.1.100 to 12.1.500, no ECCR cold start or other special action is required.

Rename Saved Search

Table of Contents

CDC Guide for z/OS

CDC Guide for z/OS

If You Migrate to DB2 12 for z/OS

If You Migrate to DB2 12 for z/OS