Journal mapping - Connect_CDC - connect_cdc_mimix_share - 5 - 5.8

Connect CDC Advanced User Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
5.8
Language
English
Product name
Connect CDC
Title
Connect CDC Advanced User Guide
Copyright
2023
First publish date
2003
ft:lastEdition
2023-09-27
ft:lastPublication
2023-09-27T18:12:55.651884

How do I handle capturing the actual update statement (and not its result) in a journal mapping?

You can do journal mapping to enable the details of any update activity on a table to be captured and recorded on a target table known as a journal. This is a log at a target server that can track the changes made to a source table, useful for auditing, for example.

Journal mapping captures the “before” values in an update statement to know what changed. Use this process if you want to check the accuracy of entries, to see, for example, if representatives are “rounding up” when they enter data, you might use journal mapping to re-create their entries and see the changes. You could also use this feature to see exactly what changes were made to the record when a phone line went down.

It is possible to replicate a source table to both a journal table and a normal target table on the same server.

Note: Journal mapping differs from the DB2 definition of journaling.