If the 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:
...
To see the SQL and other details of the transaction that is causing the conflict:
...
| Column | ||
|---|---|---|
| ||
|
...
| Panel | ||
|---|---|---|
| ||
dbvrep> LIST CONFLICT |
or by specifying the actual conflict id
...
| Column | ||
|---|---|---|
| ||
|
...
| Panel | ||
|---|---|---|
| ||
dbvrep> LIST CONFLICT 345 |
It is also possible to obtain the conflict information directly from the Dbvisit Replicate schema. Logon to the apply (target database) as the Dbvisit Replicate schema owner (dbvrep) and query table:
DBRSAPPLY_CONFLICT_LOG
This lists all the conflicts encountered, including failing SQL.
...
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 and Apply processes).
Example:
| Panel | ||
|---|---|---|
| ||
dbvrep> CHOOSE REPLICATION MINE1 |
The above command will choose the replication pair that is associated with MINE1. Typically this is MINE1->APPLY1.
Note that the CHOOSE REPLICATION command is needed prior to issuing commands to display, resolve and set conflicts for the APPLY1 process.