Replication Guide and Reference

Auditing data usage

Auditing is the need to track histories of data use, in terms of before and after comparisons of the data or identifying changes by time and by updating user ID.

IBM Replication supports auditing in the following ways:

Before and after images

When you define replication sources, you can include before-image columns of the updated rows in the target tables. A before-image copy is useful in some industries that require auditing or application rollback capability.

Maintenance of history

A noncondensed CCD table holds one row per UPDATE, INSERT, or DELETE operation, thus maintaining a history of the operations performed on the source table. If you capture UPDATEs as INSERTs and DELETEs (for partitioning key columns), the CCD table will have one row per DELETE and INSERT and two rows per UPDATE.

Transaction identification

Several columns in the CD tables and UOW table are available for audit use. You can find the approximate commit time of the changed row at the source server in the UOW table, and you can find the operation type (INSERT, UPDATE, and DELETE) in the CD table.

If you need more user-oriented identification, columns for the DB2 for OS/390 correlation ID and primary authorization ID or the AS/400 job name and user profile are available in the UOW table.

[ DB2 List of Books | Search the DB2 Books ]