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

Example 3. Minimum Rows and UOW Count

Example 3. Minimum Rows and UOW Count

This example uses the
Minimum Rows Per commit
and
UOW Count
attributes to control commit processing.
The change data consists of UOWs of the same size. Each UOW contains ten change records.
The following table describes the commitment control attribute values that this example uses:
Attribute
Value
Maximum Rows Per commit
0, which disables this attribute
Minimum Rows Per commit
100
Real-time Flush Latency in milli-seconds
-1, which disables this attribute
UOW Count
10
PWXPC passes the minimum rows value to PowerExchange and requests change data from the change stream. Because the minimum rows value is 100, PowerExchange skips the commit records of the first nine UOWs. When PowerExchange reads the last change record in the tenth UOW, the minimum rows limit is met. So, PowerExchange passes the commit record for the tenth UOW to PWXPC and resets the minimum rows counter. PWXPC increases the UOW counter to one.
PowerExchange and PWXPC continue to read the change data until the UOW counter is 10. At this point, PWXPC flushes the data buffer to commit the change data to the targets and resets the UOW counter.
PWXPC commits change data after 1,000 change records, or after every 10 UOWs, because each UOW contains 10 change records and the
UOW Count
is 10.

0 COMMENTS

We’d like to hear from you!