Replication Fails For Bulkloaded Entries With "Conflict reason: Attempted to modify a non-existent entry" (Doc ID 784429.1)

Last updated on JULY 01, 2016

Applies to:

Oracle Internet Directory - Version 10.1.4.0.1 and later
Information in this document applies to any platform.

Symptoms

Replication has been successfully configured between Master and Replica OID and the replication daemon has been started.

The $ORACLE_HOME/ldap/log/oidrepld01.log shows that new entries in the Master OID are successfully replicated to the Replica.

However the following conflicts are frequently reported for entries that were bulkloaded into the Replica from the Master OID:

2009/01/28:13:10:18 * ************ Conflict Resolution Message ************
2009/01/28:13:10:18 * Conflict reason: Attempted to modify a non-existent entry.
2009/01/28:13:10:18 * Change number:461723.
2009/01/28:13:10:18 * Supplier:cioid_orcloid.
2009/01/28:13:10:18 * Change type:Modify.
2009/01/28:13:10:18 * Target DN:cn=1000126436,cn=Users,dc=oracle,dc=com.
2009/01/28:13:10:18 * Result: Change moved to low priority queue after failing on 10th retry.

2009/01/28:13:10:19 * ************ Conflict Resolution Message ************
2009/01/28:13:10:19 * Conflict reason: Attempted to modify a non-existent entry.
2009/01/28:13:10:19 * Change number:462107.
2009/01/28:13:10:19 * Supplier:cioid_orcloid.
2009/01/28:13:10:19 * Change type:Modify.
2009/01/28:13:10:19 * Target DN:cn=1000122767,cn=Users,dc=oracle,dc=com.
2009/01/28:13:10:19 * Result: Change moved to low priority queue after failing on 10th retry.

2009/01/28:13:11:47 * ************ Conflict Resolution Message ************
2009/01/28:13:11:47 * Conflict reason: Attempted to modify a non-existent entry.
2009/01/28:13:11:47 * Change number:463110.
2009/01/28:13:11:47 * Supplier:cioid_orcloid.
2009/01/28:13:11:47 * Change type:Modify.
2009/01/28:13:11:47 * Target DN:cn=1000059965,cn=Users,dc=oracle,dc=com.
2009/01/28:13:11:47 * Result: Change moved to low priority queue after failing on 10th retry.

 

 

The Target DNs reported in the conflicts have been verified to exist in the Replica OID.

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