Listing of the conflict with the LIST CONFLICT command
...
| No Format | ||
|---|---|---|
| ||
dbvrep> LIST CONFLICT |
...
or by specifying the actual conflict id:
| No Format | ||
|---|---|---|
| ||
dbvrep> LIST CONFLICT 345 |
...
or by specifying last:
| No Format | ||
|---|---|---|
| ||
dbvrep> LIST CONFLICT LAST |
...
Viewing all the conflicts
It is also possible to obtain the conflict information directly from the Dbvisit Replicate repository. Logon to the apply APPLY (target database) as the Dbvisit Replicate schema owner (dbvrep) and query table:
| No Format | ||
|---|---|---|
| ||
DBRSAPPLY_CONFLICT_LOG |
...
The column SQL_TEXT contains the actual SQL statement that is run against the target database and includes the bind variables.
How much time is spend on the conflict
Conflicts will slow down the replication process as extra resources are required to process the conflicts
To determine how much time is spent retrying/waiting for conflicts to resolve, the following query can be used:
| No Format |
|---|
SQL> select sum (resolve_date-apply_date) from dbrsapply_conflict_log group by trunc(resolve_date); |
The query will list the sum of all conflicts. The Query can be changed to group the time for each different conflict.