Resolve the conflict. There are different options to resolve the conflict. All options can be viewed here: Resolving Current Conflict.
In our case we have to choose, which value do we need on target database. We decided, that we want to have both databases in sync, so we choose OVERWRITE method as a conflict resolution: conflict id in our case is 65010063922
dbvrep> resolve conflict 65010063922 as OVERWRITE
Use command "help resolve conflict" to view information about this command
dbvrep> help resolve conflict RESOLVE: RESOLVE CONFLICT id AS resolution: Resolve conflict on apply as IGNORE, IGNOREALL, OVERWRITE, FORCE, RETRY, RESTART, ROLLBACK or ABORT.
The conflict will be resolved. The OVERWRITE removes the "PRODUCT_NAME" condition from the WHERE clause and checks the target value only for existence of primary key column values (PRODUCT_ID).
The command console will no longer show the conflict and the apply process starts to apply other transactions:
MINE IS running. Currently at plog 65 and SCN 1490344 (02/15/2015 11:19:07). APPLY IS running. Currently at plog 65 and SCN 1490318 (02/15/2015 11:19:01) ... REPOE.PRODUCT_INFORMATION: 100% Mine:7/7 Unrecov:0/0 Applied:7/1 Conflicts:1/1
Compare both tables on source and target and verify that they are the same:
REPOE@ttorcl_src> select product_id, product_name from repoe.product_information where product_id=100;
PRODUCT_ID PRODUCT_NAME
---------- --------------------------------------------------
100 Dbvisit Replicate
REPOE@TTORCL_TRG> select product_id, product_name from repoe.product_information where product_id=100;
PRODUCT_ID PRODUCT_NAME
---------- --------------------------------------------------
100 Dbvisit Replicate
0 Comments