DIP 11g Fails to Sync Needed Objectclasses On User LDAP Modify / Replace "LDAP: error code 65"
(Doc ID 2046017.1)
Last updated on FEBRUARY 11, 2019
Applies to:
Oracle Unified Directory - Version 11.1.2.2.0 and laterOracle Internet Directory - Version 11.1.1 and later
Information in this document applies to any platform.
Symptoms
DIP fails to sync needed objectclasses on user LDAP during modify / replace.
ODIException: Error Modifying Entry in Directory
at oracle.ldap.odip.gsi.LDAPWriter.modify(LDAPWriter.java:662)
at
oracle.ldap.odip.gsi.LDAPWriter.performWriteChanges(LDAPWriter.java:471)
at oracle.ldap.odip.gsi.LDAPWriter.writeChanges(LDAPWriter.java:269)
at
oracle.ldap.odip.web.DIPSyncWriterThread.run(DIPSyncWriterThread.java:71)
Caused By: javax.naming.directory.SchemaViolationException: [LDAP: error code
65 - Entry uid=<UID>,ou=people,o=<COMPANY NAME> cannot not be modified
because the resulting entry would have violated the server schema: Entry
uid=<UID>,ou=people,o=<COMPANY NAME> violates the Directory Server schema
configuration because it includes attribute hmdynmemberof which is not
allowed by any of the objectclasses defined in that entry]; remaining name
'uid=<UID>,ou=people,o=<COMPANY NAME>'
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 |