Page Comparison

Resolve the conflict. There are different options to resolve the conflict. They can be viewed here: Resolving Current Conflict. In this our 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 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 IGNOREOVERWRITE

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. OVERWRITE removes the "PRODUCT_NAME" condition from the WHERE clause and checks the target value only for existance of primary key columns (PRODUCT_ID). 

The command console will no longer show the conflict . Note the Conflicts counter for table REPOE.SALES shows 1.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

...