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

Stopping the DB2 ECCR

Stopping the DB2 ECCR

You can stop the DB2 ECCR by issuing the ECCR QUIESCE command or the MVS STOP command.
If you use the QUIESCE command, the DB2 ECCR waits until it reaches a point in the DB2 log where no in-flight UOWs exist before shutting down. Use the QUIESCE command before performing a required cold start, for example, when migrating to a new DB2 version or upgrading PowerExchange. On a busy DB2 subsystem, quiesce processing might take a long time. To issue the QUIESCE command, use the following syntax:
F
eccr_task_name
,QUIESCE
Use the MVS STOP command to stop the DB2 ECCR immediately, even though in-flight UOWs might exist. To issue the STOP command, use the following syntax:
{STOP|P}
eccr_task_name
After you stop the ECCR, PowerExchange issues messages that report the ECCR starting RBA, the number of records sent to the PowerExchange Logger for z/OS, the RBA or LRSN of the last DB2 log record that the DB2 ECCR read, and the URID of the oldest open UOW at that location in the DB2 log.

0 COMMENTS

We’d like to hear from you!