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

Backing Up PowerExchange Condense Output Files

Backing Up PowerExchange Condense Output Files

Periodically, back up PowerExchange Condense checkpoint files, CDCT file, and condense files. If the existing files become damaged or deleted, you can then use the backups to restore the files.
Informatica recommends that you back up the checkpoint files followed by the CDCT file and then the condense files. Back up the files during a period of low activity.
The CDCT file must be backed up in coordination with the checkpoint files. For every (2
n
-1) condense cycles completed, where
n
is the number of checkpoint files that you use, you must back up the CDCT at least once. If you do not back up the CDCT file in coordination with the checkpoint files and file corruption occurs, the CDCT file and the condense files to which the CDCT file points might no longer be synchronized.
For example, if you use eight checkpoint files and perform a file switch every 20 minutes, back up the CDCT file at least every ((2 * 8) - 1) * 20 = 300 minutes. Back up the checkpoint files before they are overwritten by a later condense cycle.
The frequency with which you back up the condense files is at your discretion.

0 COMMENTS

We’d like to hear from you!