Getting Conflict Resolution Message in oidrepld.log Even though OID Replication is Working Fine (Doc ID 784372.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Internet Directory - Version 10.1.2 to 10.1.4 [Release 10gR2 to 10gR3]
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

Getting "Conflict Resolution Message" in oidrepld.log even though Replication is Working Fine between MDS and RMS.

Example:

Database ABC was successfully registered on the MDS and was automatically replicated to the RMS and is visible in the RMS.

Then unregistered the ABC database on the MDS. The ABC entry shows as removed from the MDS and the RMS.

*** HOWEVER *** one of replicated calls on the RMS from the unregister fails and Conflict Resolution Message is logged in oidrepld.log..

.............

2009/02/17:22:06:15 * ************ Conflict Resolution Message ************
2009/02/17:22:06:15 * Conflict reason: Attempted to delete a non-existent entry.
2009/02/17:22:06:15 * Change number:3214.
2009/02/17:22:06:15 * Supplier:xyz_oid1.
2009/02/17:22:06:15 * Change type:Delete.
2009/02/17:22:06:15 * Target DN:cn=DESCRIPTION_0, cn=ABC,cn=OracleContext,dc=oracle,dc=com.
2009/02/17:22:06:15 * Result: Change moved to low priority queue after failing on 10th retry.

..............................

 

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms