Table of Contents

Search

  1. Preface
  2. DTL0001 to DTL3004
  3. DTL58001 to DTL62591
  4. PWXEDM172000 to PWXEDM173002
  5. PWXEDM175000 to PWXEDM175648
  6. PWXEDM176400 to PWXEDM177699
  7. PWXEDM181200 to PWXEDM181599
  8. PWXEDM261000 to PWXEDM263999
  9. Abend, Return, and Reason Codes in PowerExchange Messages

Message Reference Volume 3

Message Reference Volume 3

PWXEDM 177578 I

PWXEDM
177578
I

Clone '
creator
.
table_name
' is {added to | dropped from | exchanged with} table '
creator
.
table
' at
timestamp
When the DB2 ECCR was processing DB2 log records, it detected that a clone table was added, dropped, or exchanged with its base table. The ECCR is currently capturing changes for the base table. This message provides the clone table name, base table name, and the timestamp for when the clone table change occurred. The timestamp format is yyy-mm-dd-hh.mm.ss.mmmmmm.
Processing continues. The DB2 ECCR continues to capture changes for the base table but does not capture changes for the associated clone table. If the clone table and base table have been exchanged, the ECCR captures changes from the new instance of the table.
The informational message is issued to help properly track the tables from which data is captured. If the clone table and base table have been exchanged, additional action might be required. The change data that the ECCR captures from the new instance of the table might be inconsistent with the change data that was captured from the previous instance of the table. If so, data inconsistency problems might occur when you attempt to apply the newly captured change data to the targets. To resolve this problem, rematerialize the targets.

0 COMMENTS

We’d like to hear from you!