My Oracle Support Banner

OID Replication Fails. Replication Log Message: Conflict Resolution Message | Conflict reason: Parent entry does not exist. or Conflict reason: System error encountered: Type or value exists. (Doc ID 2276514.1)

Last updated on NOVEMBER 17, 2019

Applies to:

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

Symptoms

After configuring Replication between two Oracle Internet Directory (OID) servers, seeing the following replication log errors:

Log message for a parent container/tree change:

[2017-06-12T09:24:02.167752-04:00] [OID] [NOTIFICATION:16] [] [OIDREPLD] [host: <OID HOSTNAME>] [pid: <PID>] [tid: <TID>] Worker(Transport)::[[************ Conflict Resolution Message ************
Conflict reason: Parent entry does not exist.
Change number: 1234567.
Supplier: <HOSTNAME>_<SID>.
Change type: Add.
Target DN: cn=users,dc=<COMPANY>,dc=com.
Result: Change moved to low priority queue after failing on 10th retry.
]]

Log message for an entry change:

[2017-09-18T16:11:28.283984-04:00] [OID] [NOTIFICATION:16] [] [OIDREPLD] [host: <OID HOSTNAME>] [pid: <PID>] [tid: <TID>] Worker(Transport)::[[************ Conflict Resolution Message ************
Conflict reason: Attempted to modify a non-existent entry.
Change number: 1234568.
Supplier: <HOSTNAME>_<SID>.
Change type: Modify.
Target DN: cn=<ENTRY>,cn=Users,dc=<COMPANY>,dc=com.
Result: Change moved to low priority queue after failing on 10th retry.
]]

Or:

[2019-07-30T14:09:38.934443-04:00] [OID] [NOTIFICATION:16] [] [OIDREPLD] [host: <OID HOSTNAME>] [pid: <PID>] [tid: <TID>] Worker(Transport)::[[************ Conflict Resolution Message ************
Conflict reason: System error encountered: Type or value exists.
Change number: 123456.
Supplier: <HOSTNAME>_<SID>.
Change type: Modify.
Target DN: cn=<ENTRY>,cn=Users,dc=<COMPANY>,dc=com.
Result: Change moved to low priority queue after failing on 10th retry.
]]

Replication may fail for all entries, or may be able to successfully edit existing user entry attributes and the changes are replicated to the other node, but not add or delete new entries which report the log errors above.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.