The response to a conflict can be configured before the conflict occurs. This is done with conflict handlers. The configuration can be specified for each replicated table and for each operation type separately, and for the special case ("data divergence" divergence) when zero or more than one row are affected. The Dbvisit Replicate command to set conflict handlers is SET_CONFLICT_HANDLERS.

...

The default global setting for conflicts is "retry". This means that the operation will keep trying the operation until a manual change is made on the target to resolve the conflict.

DISCARD and IGNORE handlers are synonyms.

The transaction handler is used for errors in DDL and during commit/rollback.

...

dbvrep> help set_conflict_handlers
SET_CONFLICT_HANDLERS: Set apply conflict handlers.
SET_CONFLICT_HANDLERS FOR TABLE owner.name FOR operation ON type TO handler [logging] [additional info]
SET_CONFLICT_HANDLERS FOR DEFAULT FOR operation ON type TO handler [logging] [additional info] owner.name is name of the table on SOURCE database, use
DEFAULT to set it for future added/created tables
operation is one of UPDATE, DELETE, INSERT, TRANSACTION
type is one of ERROR, TOO_MANY, NO_DATA (TOO_MANY and NO_DATA available for UPDATE or DELETE only)
handler is one of RETRY, PAUSE, ABORT, DISCARD, FORCE, OVERWRITE, PLSQL, SQL, NEWER, OLDER (NEWER and OLDER available for DATA type only)
logging is one of LOG, NOLOG, FAST_NOLOG, LOG_TRANSACTION (FAST_NOLOG may optimize processing and not update conflict counters)
Additional info is 'BY COLUMNS comma-delimited-column-list 'for NEWER/OLDER, 'full-procedure-name' for PLSQL and 'regular expression' for SQL.

Default values

Default values for all available conflict types are defined by the following variables:

_DEFAULT_HANDLER_UPDATE_NO_DATA
_DEFAULT_HANDLER_UPDATE_TOO_MANY
_DEFAULT_HANDLER_UPDATE_ERROR

_DEFAULT_HANDLER_DELETE_NO_DATA
_DEFAULT_HANDLER_DELETE_TOO_MANY
_DEFAULT_HANDLER_DELETE_ERROR

_DEFAULT_HANDLER_INSERT_ERROR
_DEFAULT_HANDLER_TRANSACTION_ERROR

These variables are used for both tables and default conflict handlers.  This default value is used when there are no conflict handlers defined for a given table for a given conflict.  For example, the default value for _DEFAULT_HANDLER_INSERT_ERROR is retry.  You can change the default value to another value (see chart above), creating a new default value. For example, you could set it to DISCARD.  Discard will be the new default for all table. If you desire a certain table to not have discard and have another option, PAUSE, for example you can set a conflict handers for that individual table and leave the default (that you set) alone.

To set the conflict handlers for a given table (or to set default conflict handlers) to the default values (determined by the variables shown above) use UNSET_CONFLICT_HANDLERS command (see Full Command-Line Reference).

Examples

dbvrep> SET_CONFLICT_HANDLERS FOR TABLE SCOTT.AVI_OBJECTS FOR UPDATE ON NO_DATA TO OVERWRITE

dbvrep> show_conflict_handlers for table scott.avi_objects 
The table called SCOTT.AVI_OBJECTS on source is handled on apply as follows:
UPDATE (error): handler: RETRY logging: LOG
UPDATE (no_data): handler: OVERWRITE logging: LOG
UPDATE (too_many): handler: OVERWRITE logging: LOG
DELETE (error): handler: RETRY logging: LOG
DELETE (no_data): handler: RETRY logging: LOG
DELETE (too_many): handler: RETRY logging: LOG
INSERT (error): handler: RETRY logging: LOG
TRANSACTION (error): handler: RETRY logging: LOG

create table scott.x (i number);
insert into x values (1);
insert into x values (1);
commit;

update x set i=2 where i=1; 
commit;

(#1) update x set i=2 where i=1;
(#2) update x set i=2 where i=1;

SET_CONFLICT_HANDLERS FOR TABLE SCOTT.X FOR UPDATE ON TOO_MANY TO SQL s/$/ and rownum = 1/

SET_CONFLICT_HANDLERS FOR TABLE SCOTT.X FOR DELETE ON TOO_MANY TO SQL s/$/ and rownum = 1/