My Oracle Support Banner

OUD - Object Class Violation - When Attempting to Add a Custom Attribute to an Entry And When the Custom Objectclass (That Allows the Custom Attribute) Was Added Using the ldapmodify Command (Doc ID 2570546.1)

Last updated on AUGUST 09, 2019

Applies to:

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


Not able to add an attribute to an entry.

Result Code: 65 (Object Class Violation)

The issue can be reproduced at will with the following steps:
Run the below command after adding custom schema that includes the custom objectclass and custom attribute -
$ ./ldapmodify -p 5491 -D "cn=directory manager" -w <PASSWORD> -f addBadAtt.ldif
Processing MODIFY request for cn=testuser,ou=people,dc=example,dc=com
MODIFY operation failed
Result Code:  65 (Object Class Violation)
Additional Information:  Entry cn=testuser,ou=people,dc=example,dc=com cannot not be modified because the resulting entry would have violated the server schema:  Entry cn=testuser,ou=people,dc=example,dc=com violates the Directory Server schema configuration because it includes attribute <CUSTOM_ATTRIBUTE> which is not allowed by any of the objectclasses defined in that entry

The issue has the following business impact:
Due to this issue, can not add the custom attribute to an entry.




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

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