| Note |
|---|
To view the conflicts, please see Viewing the conflicts |
...
IGNORE | Skip the change (the conflicting statement is rolled back). |
FORCE | Skip the change (the conflicting statement is kept applied) - – this is different from IGNORE only if the statement acutally actually did change something, i.e. only if it updated/deleted more than one row. (For any other conlictconflict: either Oracle rolls the statement back automatically due to an ORA- error or the conflict was 0 rows updated - updated – thus no change was actually done.) |
OVERWRITE | Try again, not checking the old (source) values in the where clause. This overwrites the target database with the values from the source database. The OVERWRITE handler is used for conflicts with UPDATE statements. OVERWRITE works by using only Primary Key (PK) columns in the where clause. If the record to be updated is still not found on the target (by using only the PK columns in the where clause), the UPDATE cannot proceed and OVERWRITE will have no affecteffect. |
RETRY | Try again. |
ABORT | Abort the APPLY whole process. |
RESTART | Rollback and restart the transaction. |
ROLLBACK | Rollbacks the transaction. |
IGNOREALL | The current and future conflicts in the same transaction will be resolved as ignore. |
Global default conflict handler
...
By default all commands in the Dbvisit Replicate console work with the default processes MINE and APPLY. The choose CHOOSE replication command is useful when working with 2-way replication where there are multiple processes such as MINE, APPLY, MINE1 and APPLY1.
...
| No Format | ||
|---|---|---|
| ||
dbvrep> CHOOSE REPLICATION MINE1 |
The above command will choose the replication pair that is associated with MINE1. Typically this is MINE1->APPLY1.
| Note |
|---|
The CHOOSE REPLICATION command is needed prior to issuing commands to display, resolve and set conflicts for the APPLY1 process. |
...