Staging Table Options - Fields and controls

Unit of work (UOW) columns

Select to specify that your staging table will be noncomplete and will include the following extra columns from the UOW table:

IBMSNAP_APPLY_QUAL

This column prevents circular replication during update-anywhere processing. It remains blank for local updates, but contains the name of the associated Apply program for updates that are made by the Apply program for an update-anywhere subscription set. The Capture program derives this value from the critical section table.

IBMSNAP_AUTHID

This column shows the authorization ID that is associated with the transaction. It is useful for database auditing. For DB2 for OS/390, this column is the primary authorization ID. For DB2 for AS/400, this column has the name of the user profile ID under which the application that caused the transaction ran. This column holds a 10-character ID padded with blanks. This column is not automatically copied to other tables; you must select it and copy it as a user data column. This user data column should be a CCD target type.

IBMSNAP_AUTHTKN

This column shows the authorization token associated with the transaction. This ID is useful for database auditing. For DB2 for OS/390, this column is the correlation ID. For DB2 for AS/400, this column is the job name of the job that caused a transaction. This column is not automatically copied to other tables; you must select it and copy it as a user data column. This user data column should be a CCD target type.

IBMSNAP_REJ_CODE

This column is set only during update-anywhere replication if conflict detection is specified as standard or advanced when you define your replication source.

0

A transaction with no known conflict.

1

A transaction that contains a conflict where the same row in the source and replica tables have a change that was not propagated. When a conflict occurs, the transaction will be reversed at the replica table.

2

A cascade-rejection of a transaction dependent on a prior transaction having a least one same-row conflict. When a conflict occurs, the transaction will be reversed at the replica table.

3

A transaction that contains at least one referential-integrity constraint violation. Because this transaction violates the referential constraints defined on the source table, the Apply program will mark this subscription set a failed. Updates cannot be copied until the referential integrity definitions are corrected.

4

For a cascade-rejection of a transaction dependent on a prior transaction having at least one constraint conflict.

IBMSNAP_UOWID

This column shows the unit-of-work identifier from the log record header for this unit of work.

0	A transaction with no known conflict.
1	A transaction that contains a conflict where the same row in the source and replica tables have a change that was not propagated. When a conflict occurs, the transaction will be reversed at the replica table.
2	A cascade-rejection of a transaction dependent on a prior transaction having a least one same-row conflict. When a conflict occurs, the transaction will be reversed at the replica table.
3	A transaction that contains at least one referential-integrity constraint violation. Because this transaction violates the referential constraints defined on the source table, the Apply program will mark this subscription set a failed. Updates cannot be copied until the referential integrity definitions are corrected.
4	For a cascade-rejection of a transaction dependent on a prior transaction having at least one constraint conflict.