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

Recovering the DB2 ECCR

Recovering the DB2 ECCR

You can recover the DB2 ECCR if it fails or if the PowerExchange Logger for z/OS stops or fails while attached to the ECCR.
When the PowerExchange Logger stops or abends while attached to the ECCR, the ECCR also abends when it receives the first change record after the PowerExchange Logger failure.
  1. Determine the cause of the DB2 ECCR failure.
    The EC PERMIL statement in the REPL2OPT DD data set indicates the maximum number of errors that the ECCR tolerates before ending.
  2. Correct the error.
    If the DB2 ECCR failed because the PowerExchange Logger ended, restart the PowerExchange Logger.
  3. Restart the DB2 ECCR from the point at which it abended.
    Specify the STARTUP WARM statement in the REPDB2OPT DD data set. Use the same REPL2CTL file that you used prior to the abend.
When you restart the DB2 ECCR or the PowerExchange Logger, the PowerExchange Logger determines the point at which to resume capturing changes for the corresponding CA name.

0 COMMENTS

We’d like to hear from you!