All keywords are case-insensitive.
...
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.
Example:
No Format | ||
---|---|---|
| ||
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> |
...
No Format | ||
---|---|---|
| ||
dbvrep> shutdown mineall Upon restart MINE will go back to redolog 4873 (thread 1), going back 1 log. Upon restart APPLY will go back to plog 4873, going back 1 plog. Are you sure you want to shutdown? (Yes/No) [No] dbvrep> shutdown mine Dbvisit Replicate mine process shutting down. dbvrep> dbvrep> shutdown all Upon restart MINE will go back to redolog 4873 (thread 1), going back 1 log. Are you sure you want to shutdown? (Yes/No) [No] dbvrep> shutdown immediate all Dbvisit Replicate APPLYMINE process shutting down. Dbvisit Replicate MINEAPPLY process shutting down. dbvrep> |
Anchor | ||||
---|---|---|---|---|
|
...