Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Resolve the conflict. There are different options to resolve the conflict. They can be viewed here: Resolving Current Conflict. In this case because we already updated the target, so at this moment the values are the same on target as well as on source, we will choose IGNORE as a resolve conflict handler: In this case the conflict ID is 65010063922 

dbvrep> resolve conflict 65010063922 as IGNORE

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 IGNORE throws the conflicting update and enables the apply process to continue apply other changes. The command console will no longer show the conflict. Note the Conflicts counter for table REPOE.SALES shows 1.

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

  • No labels