OUD11g/12c - Inconsistent Behavior while Using "uniqueMember" Attribute in a Custom ObjectClass
(Doc ID 2725604.1)
Last updated on DECEMBER 20, 2022
Applies to:
Oracle Unified Directory - Version 12.2.1.3.180829 and laterInformation in this document applies to any platform.
Symptoms
In a replication environment, when trying to add a new value for uniqueMember attribute in a custom objectclass, the result of the add operation is OK (added), but then, when searching for that value, the value is missing. The same behavior is not seen in a non-replication environment.
Changes
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 |
Changes |
Cause |
Solution |
References |