Table of Contents

Search

  1. Preface
  2. Part 1: PowerExchange Change Data Capture Introduction
  3. Part 2: CDC Components Configuration and Management
  4. Part 3: CDC Sources Configuration and Management
  5. Part 4: Change Data Extraction
  6. Part 5: Monitoring and Tuning
  7. Appendix A: CDC for z/OS Troubleshooting
  8. Appendix B: DTL__CAPXTIMESTAMP Time Stamps

Upgrading the DB2 ECCR Capture Directory Tables

Upgrading the DB2 ECCR Capture Directory Tables

You might need to upgrade the DB2 ECCR capture directory tables before migrating to DB2 11.
To determine whether you need to upgrade the capture directory tables, look for message PWXEDM177552I in the message output from DB2 ECCR initialization. This message identifies the latest DB2 version that your capture directory tables support.
Do not change the schemas of any DB2 tables that are registered for change data capture until
after
you upgrade the capture directory tables and restart the DB2 ECCR.
To properly upgrade the capture directory tables, complete the following steps:
  1. If the DB2 ECCR is running, use the QUIESCE command to stop it.
  2. Customize the SQL statements in the sample EXPNDC51 member in the SAMPLIB library.
    This SQL creates copies of the current capture directory tables prior to upgrading them.
  3. Use SPUFI or a batch SQL utility to execute the SQL statements in the modified EXPNDC51 member.
  4. Customize the SQL statements in the sample EXPNC5L2 or EXPNC5R2 member in the SAMPLIB library.
    Use the EXPNC5L2 member in a data sharing environment, or use the EXPNC5R2 member in a non-data-sharing environment. These members drop the old capture directory tables and create new capture directory tables that support DB2 11. For more information, see the comments in these members.
  5. Use SPUFI or a batch SQL utility to execute the SQL statements in the modified EXPNC5L2 or EXPNC5R2 member.
  6. Warm start the DB2 ECCR.
    The ECCR resumes change data capture with the upgraded catalog capture directory tables.
You can now migrate your subsystem to DB2 11.

0 COMMENTS

We’d like to hear from you!