Table of Contents

Search

  1. Preface
  2. Change Data Capture Introduction
  3. PowerExchange Listener
  4. PowerExchange Condense
  5. DB2 for i5/OS Change Data Capture
  6. Remote Logging of Data
  7. Introduction to Change Data Extraction
  8. Extracting Change Data
  9. Monitoring CDC Sessions
  10. Managing Change Data Extractions
  11. Tuning CDC Sessions
  12. Appendix A: DTL__CAPXTIMESTAMP Time Stamps

CDC Guide for i5/OS

CDC Guide for i5/OS

Refreshing the CDC Interest List After Adding or Deleting Libraries

Refreshing the CDC Interest List After Adding or Deleting Libraries

If you have multiple instances of a DB2 for i5/OS source table that are journaled to the same user journal and you routinely add or delete libraries that contain a table instance, you can refresh the CDC library interest list with minimal interruption to real-time extraction processing and PowerCenter workflows.
The source table instances must be journaled to the same local user journal, and this journal must be one that PowerExchange is currently using.
This feature is intended for users who add or delete a large number of libraries on a routine basis. Without the refresh feature, when you delete a library from which data is captured, PowerExchange real-time extraction processing stops, causing the PowerCenter workflow to end abnormally. When you add a library, the CDC session does not start processing change data for the new library until you stop and restart the PowerExchange Listener and PowerCenter workflow. Use the refresh feature to avoid these downtime conditions and associated delays.
To enable refresh processing, you must configure the following PowerCenter and PowerExchange parameters:
  • In PowerCenter, enter the asterisk (*) wildcard for the library name in the
    Library/File Override
    session property for the real-time CDC session. This library name override enables the session to read changes for all of the table (file) instances across multiple libraries, including any library you add. You can specify the table just once in the mapping.
  • In PowerExchange, set the ALWLIBRFSH parameter to Y in the AS4J CAPI_CONNECTION statement of the DBMOVER member. This setting enables you to issue refresh requests with the SNDPWXJRNE command.
Other recommended DBMOVER parameters are the AS400USRJRNCODE statement, the AS400EVENTMSGQ statement, and the LIBASUSER parameter in the AS4J CAPI_CONNECTION statement.
After you add or delete libraries, use the PowerExchange SNDPWXJRNE command to issue a refresh request from the
i5/OS
console. PowerExchange writes messages to the PowerExchange message log file in the
datalib
library or optionally to the AS400EVENTMSGQ event message queue for audit and monitoring purposes.

0 COMMENTS

We’d like to hear from you!