Oracle GoldenGate Conflict Detection and Resolution (CDR) has two parts: Conflict Detection and Conflict Resolution. Before starting with conflict resolution, it's important to investigate and complete conflict detection.

Oracle GoldenGate Conflict Detection and Resolution (CDR) provides basic conflict resolution routines that:

• Resolve a uniqueness conflict for an INSERT.

• Resolve a "no data found" conflict for an UPDATE when the row exists, but the before image of one or more columns is different from the current value in the database.

• Resolve a "no data found" conflict for an UPDATE when the row does not exist.

• Resolve a "no data found" conflict for a DELETE when the row exists, but the before image of one or more columns is different from the current value in the database.

• Resolve a "no data found" conflict for a DELETE when the row does not exist.

To use conflict detection and resolution (CDR), the target database must reside on a Windows, Linux, or UNIX system. It is not supported for databases on the NonStop platform.

 CDR supports scalar data types such as:

• NUMERIC

• BOOLEAN

• DATE

• TIMESTAMP

• CHAR/NCHAR

• VARCHAR/ NVARCHAR

This means that these column types can be used with the COMPARECOLS parameter and as the resolution column in the USEMIN and USEMAX options of the RESOLVECONFLICT parameter. Only NUMERIC columns can be used for the USEDELTA option of RESOLVECONFLICT. For USEMAX, USEMIN, only TIMESTAMP and NUMBER are supported.

Conflict resolution is not performed when Replicat operates in BATCHSQL mode. If a conflict occurs in BATCHSQL mode, Replicat reverts to GROUPTRANSOPS mode, and then to single-transaction mode. Conflict detection occurs in all three modes.