| Note |
|---|
To view the conflicts, please see Viewing the conflicts |
If the apply APPLY was paused due to a conflict, or it is retrying in a loop the same SQL again and again, you can instruct it about what to do next using the command:
...
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 did change something, i.e. only if it updated/deleted more than one row. (For any other conlict: either Oracle rolls the statement back automatically due to an ORA- error or the conflict was 0 rows 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. |
RETRY | Try again |
ABORT | Abort the apply 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 |
...
By default all commands in the Dbvisit Replicate console work with the default processes MINE and APPLY. The choose replication command is useful when working with 2-way replication where there are multiple processes such as MINE, APPLY, MINE1 and APPLY1.
Note that the CHOOSE REPLICATION command selects all processes for the indicated replication (so both Mine MINE and Apply APPLY processes).
Example:
| 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. |
...