Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

All keywords are case-insensitive.

...

Anchor
SET_CONFLICT_HANDLERS
SET_CONFLICT_HANDLERS
SET_CONFLICT_HANDLERS


Image RemovedImage AddedImage Added

Image Removed

Image Removed

Image Removed

Image Removed


Image RemovedImage AddedImage Added

Image AddedImage Added

Note

Setting logging option for conflict handlers to value of NOLOG, FAST_NOLOG , or LOG_TRANSACTION is not supportedno longer supported. Use NOLOG or LOG instead.

Gets object id as of current MINE progress and sets conflict handlers for this table (schema.name refers to current table name at MINE).

The DEFAULT conflict handler will not be applied to existing prepared (replicated) tables. The DEFAULT conflict handler will only be applied to tables that are prepared after the DEFAULT conflict handler is set. To change the conflict handler for existing prepared tables, each table has to be individually set using FOR TABLE conflict handler.

The column(s) specified in the by columns clause in newer/older handlers

must not be a LOB or LONG data type.

Example:

 

No Format
bgColorCCC
dbvrep> SET_CONFLICT_HANDLERS FOR TABLE SCOTT.DEPT FOR UPDATE on NO_DATA TO OVERWRITE                                                                           
Connecting to running apply: [The table called SCOTT.DEPT on source is handled on apply (APPLY) as follows:
UPDATE (error): handler: RETRY logging: LOG
UPDATE (no_data): handler: OVERWRITE logging: LOG
UPDATE (too_many): handler: RETRY 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]
dbvrep>  

...