Conflict reported by APPLY process - ROLLED BACK ON SOURCE

Owned by Clive Otten (Unlicensed)
Jan 22, 2020

Problem Description

APPLY process reporting conflict:

APPLY IS running. Currently at plog 67609 and SCN 6823671700 (05/24/2013 17:23:58) and 1 apply conflicts so far (last at 24/05/2013 17:15:44).

Console shows the following:

ADVDBV.EA_CA_CAMPAIGN: 100% Mine:9/9 Unrecov:0/0 Applied:9/9 Conflicts:1/1 Last:24/05/2013 17:19:29/OK

And trying to list the conflicts shows nothing:

dbvrep> list conflict No current conflict and no conflict specified by the command.

How can I find details about the conflict? How do I know if any changes are missing on the destination?

Solution

Please use the command: list conflict last to see the conflict. The conflict was apparently resolved automatically. The output of "list conflict last" will give you a direction regarding possible data divergence in the conflict.

Question

Using list conflict last we get the following:

Does the message "Handled as: ROLLED BACK ON SOURCE" mean that the problem is solved on source and no inconsistencies exist on target?

Answer

The "ROLLED BACK ON SOURCE" means that the same error occurred on the source system and was rolled back. That is why it was automatically rolled back on the target as well. It was listed as a conflict so that you know this has happened.

Arjen Visser  May 25, 2013 12:05