DB2 Replication Guide and Reference

Auditing Requirements

Auditing requirements relate to the need to track histories in terms of before and after comparisons and identification of changes by time and updating user ID.

IBM Replication supports auditing in the following ways:

• Before and after images - When you define replication sources, you declare whether or not before or after image columns of the updated rows are available to subscribers. 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 building a history.

• Transaction identification - Each captured change row is automatically stamped with control columns, which are available for audit usage. Two of these columns are the approximate commit time of the changed row at the source server and the operation code (I=Insert, U=Update and D=Delete).

  If more user-oriented identification is required, columns for the DB2 correlation ID (if DB2 for MVS is the source database) and the primary authorization ID can be requested in the copy table.

[ DB2 List of Books | Search the DB2 Books ]