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

Flush Latency

Flush Latency

PowerExchange reads change data into a buffer on the source system, or into a buffer on the PowerCenter Integration Service machine if you use offload processing. The PowerExchange Consumer API (CAPI) periodically flushes the buffer to transfer the change data to PWXPC on the PowerCenter Integration Service machine.
The CAPI flushes the buffer to PWXPC when the one of the following events occurs:
  • The buffer becomes full.
  • The CAPI timeout value that is specified by the
    PowerExchange Latency in seconds
    attribute on the PWX CDC Real Time connection expires.
  • A commit point occurs.
To specify the flush latency for CDC sessions that run in real-time or continuous extraction mode, set the
PWX Latency in seconds
attribute on the PWX CDC Real Time application connection. This attribute specifies the maximum time that PowerExchange waits for more change data before flushing data to PWXPC. This attribute applies to PowerExchange on the source system, or to the PowerExchange client on the PowerCenter Integration Service machine if you use offload processing.
For CDC sessions that use batch extraction mode, PowerExchange always uses 2 seconds for the flush latency.
PowerExchange writes message PWX-09957 to the PowerExchange message log to identify the CAPI timeout value based on the
PWX Latency in seconds
attribute. If you select
Retrieve PWX Log Entries
on the application connection, PWXPC also writes this message in the session log.
After PowerExchange flushes the change data, PWXPC provides the data to the source qualifiers in the CDC session for further processing. Then the PowerCenter Integration Service commits the data to the targets.
The
PWX Latency in seconds
value also affects how fast a CDC session responds to a stop command from Workflow Monitor or pmcmd program. Before PWXPC can process a stop request, it must wait for PowerExchange to return control to it. Use the default value of 2 seconds for the
PWX Latency in seconds
attribute to avoid unacceptable delays in stop command processing.

0 COMMENTS

We’d like to hear from you!