Available handlers
| Handler | Description |
|---|---|
| DISCARD | Ignore the offending SQL and continue with the next one |
| FORCE | Ignore the conflict, leave the SQL applied and continue with the next one (this differs from DISCARD only if the SQL actually changes something, i.e. the conflict is "too many rows updated/deleted") |
| OVERWRITE | Do not check old values, try again with just primary key in the where clause (this will fail if there is no row at all on APPLY with the PK value). This will have no effect if the Primary Key was the only column represented in the where clause. Be careful if the table has no primary key. |
| NEWER,OLDER | Look into target table (by primary key) and get values of specified columns (usually dates or number sequence). If the source row is newer/older, the operation becomes OVERWRITE, otherwise DISCARD. |
| PLSQL | Call user-specified PL/SQL function. More information is available in PL/SQL conflict handler section. |
| SQL | Specify a regular expression to change the executed SQL. Note that APPLY will still bind the same variables to execute the modified statement, so instead of simply commenting them out you can use e.g. nvl(1, :1) = 1 instead. Simple example: "s/$/ and rownum = 1/" will add the specified text to end of the SQL statement. |
| RETRY | Wait a set amount of time and try again. Time is determined by the parameter RETRY_TIME. |
| PAUSE | Wait for manual user resolution |
| ABORT | Kill APPLY process |
| ERROR | Rollback the transaction, continue applying other transactions |
Note: All the configured conflict handlers are listed in table: DBRSAPPLY_CONFLICT_HANDLERS.
This has the same result running the command: dbvrep> SHOW_CONFLICT_HANDLERS
See the Command Reference or use HELP SET_CONFLICT_HANDLERS for the exact syntax.