CDC Guide for i5/OS

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

Back Next

Stopping DB2 CDC

You might need to stop change data capture for DB2 sources to perform troubleshooting or routine maintenance tasks or to remove a source permanently from CDC processing.

To stop change data capture, use one of the following methods:

To stop change capture for a registered source table, open the capture registration for the table, and change the

Status

option from

Active

History

After you set the status to

History

, you cannot activate the registration again. This status change permanently stops change data capture based on the capture registration. If you need to capture change data for the table again, you must create another capture registration.

If you use PowerExchange Condense, use the SHUTCOND or SHUTDOWN command to stop the PowerExchange Condense job. This action stops the logging of changes in the condense files for all sources of interest. When you restart PowerExchange Condense, it resumes from the current end-of-log (EOL) or from where it left off in the change stream, based on whether you cold start or warm start it.

For CDC sessions that use real-time extraction mode, stop the PowerCenter workflow to stop the replication of changes for all sources of interest. When you restart the workflow, it resumes from the current EOL or from where it left off in the change stream based on whether you cold start or warm start it.

If you do not stop updates to the source prior to stopping CDC, you might lose change data. However, if you stop and then warm start PowerExchange Condense or a PowerCenter workflow, PowerExchange can resume processing changes from where it left off and no changes are lost.

Rename Saved Search

Table of Contents

CDC Guide for i5/OS

CDC Guide for i5/OS

Stopping DB2 CDC

Stopping DB2 CDC