Missing GETBEFORECOLS with conflict detection enabled in target table

While we are configuring different environments, we sometimes will change the target to which a datapump points. While using INTEGRATED TRANLOG and the new built-in conflict resolution in GG 11.2.0.1, we found that the new replicat wouldn’t respect the before images generated by the extract. We found the following in our ggserr.log file:

2012-06-11 14:22:00  ERROR   OGG-01921  Oracle GoldenGate Delivery for Oracle, corer.prm:  Missing GETBEFORECOLS with conflict detection enabled in target table ATGDB_EXPRESS_CORE_REP.DCS_INVENTORY.

We used logdump on the source extract trail and could clearly see the before image in the trail file, so I don’t know what the replicat couldn’t find that it thought it needed. The before image definitely wasn’t in the replicat trail file.

The only way to resolve this was to delete and re-add the extract process on the source. The replicat then happily proceeded. There has to be something we are missing, but this may help if you get in a pinch.

2 comments for “Missing GETBEFORECOLS with conflict detection enabled in target table

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.