Conflict detection

Select one of the following radio buttons to determine the conflict detection level for user tables and all associated replicas:

None

If you do not want to monitor conflict detection.

Conflicting updates between the origin table and the replica will not be detected.

Standard

If you want moderate conflict detection monitoring in which the Apply program searches rows already captured in the replica's change data tables for conflicts. This is the default.

Enhanced

For conflict detection monitoring that guarantees data integrity among all replicas and the origin table. Apply locks all replicas in the subscription set against further transactions, and begins detection after all changes prior to locking are captured.

Conflict detection does not guarantee data integrity for read dependencies. For example, an application reads the replica's updated row before it is replicated back to the source table. If the transaction for the update is later rejected as a conflict, conflict detection cannot detect this conflict.

[ Top of Page | Table of Contents | Glossary | Index ]

[ DB2 List of Books | Search the DB2 Books ]