DIP Dirsync Synchronization Fails With Error [Ldap: Error Code 65 - orclSamAccountName Attribute Not Found....] (Doc ID 1267130.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Internet Directory - Version: 10.1.4 and later   [Release: 10gR3 and later ]
Information in this document applies to any platform.

Symptoms


Oracle Internet Directory (OID) Directory Integration and Provisioning (DIP) DirSync method synchronization from Active Directory (AD) to OID fails when synchronizing a MODIFY operation for an AD entry if the entry does not yet exist in OID.

DIP synchronization fails with [LDAP: error code 65 - <name> attribute not found]. The attribute named may differ depending on the synchronization profile mapping configuration. 

It has been verified that the AD entry has a value set for the attribute that is mapped to the OID attribute named in the LDAP 65 error. Configuring the Required Attribute flag for the attribute mapping does not resolve the issue.


Example entries from the synchronization profile debug trace log when the error occurs:

....
DN : cn=john smith,ou=it management,cn=users,dc=oracle,dc=com
Searching for entry in Naming context:
Normalized DN : cn=john smith,ou=it management,cn=users,dc=oracle,dc=com
Changetype is ADDRMODIFY
Processing modifyRadd Operation ..
Entry Not Found. Converting to an ADD op..
Processing Insert Operation ..
Performing createEntry..
Exception creating Entry : javax.naming.directory.SchemaViolationException:
[LDAP: error code 65 - orclSAMAccountName attribute not found. Mandatory Attribute missing.]; remaining name '"cn=john smith,ou=it management,cn=users,dc=oracle,dc=com"'
[LDAP: error code 65 - orclSAMAccountName attribute not found. Mandatory Attribute missing.]
javax.naming.directory.SchemaViolationException: [LDAP: error code 65 - orclSAMAccountName attribute not found. Mandatory Attribute missing.];
remaining name '"cn=john smith,ou=it management,cn=users,dc=oracle,dc=com"'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3019)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2934)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2740)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:777)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:236)
at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:176)
at oracle.ldap.odip.gsi.LDAPWriter.createEntry(LDAPWriter.java:1214)
at oracle.ldap.odip.gsi.LDAPWriter.insert(LDAPWriter.java:429)
at oracle.ldap.odip.gsi.LDAPWriter.modifyRadd(LDAPWriter.java:826)
at oracle.ldap.odip.gsi.LDAPWriter.writeChanges(LDAPWriter.java:353)
at oracle.ldap.odip.engine.AgentThread.mapExecute(AgentThread.java:656)
at oracle.ldap.odip.engine.AgentThread.execMapping(AgentThread.java:377)
at oracle.ldap.odip.engine.AgentThread.run(AgentThread.java:238)
DIP_LDAPWRITER_ERROR_CREATE



Steps to reproduce

1. Configure DirSync method DIP synchronization from AD to OID.
2. Create a new user entry in AD e.g. test_user. 
3. Monitor DIP synchronization and verify that the test_user entry is successfully created in OID. 
4. Delete the test_user entry in OID. 
5. In AD, make a small change to user test_user e.g. add an inital. 
6. Monitor the DIP synchronization profile log to see the error occur. 



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