All keywords are case-insensitive.
...
Set filtering rules for an already prepared table/schema. The usual way how to configure filtering is using Setup wizard (which in turn uses this very command).
NOTE ** DO NOT put a semicolon after the command in the console or upon restart of APPLY process it will not start & create support package.
If OFFLINE is used, APPLY/MINE will pick the change on the next start. Use OFFLINE if the APPLY and MINE are not running, as some network configurations may cause long timeouts while PREPARE tries to connect to the APPLY/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.
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> |
...