Page Comparison

...

dbvrep> list conflict                                                                                                                                                           
Information for conflict 724010046998 (current conflict):
Table: OEREPOE.SALES at transaction 001e.008.00000060 at SCN 3144514
SQL text (with replaced bind values): update OE"REPOE"."SALES"
set AMOUNT_RECEIVED = 120
where (1=1)
and AMOUNT_RECEIVED IS NULL 
and PROD_ID = 101
Error: Command affected 0 row(s).
Handled as: PAUSERETRY
Conflict repeated 218 times.

8. As can be seen from the SQL statement in the above list conflict, the SQL statement contains the OLD value of "AMOUNT_RECEIVED IS NULL". This is the reason for the "Command affected 0 rows". The AMOUNT_RECEIVED was updated from NULL to 60 on the target database in step 1 and so the original value of "AMOUNT_RECEIVED IS NULL" is no longer valid. In order to detect such changes in the data, the replication has added the old value of the value to be update in the WHERE predicate. This is true for most logical replication technologies.

...