OAM 11g: Oiddas Ldap Error Code 32 - No Such Object; Remaining Name 'dc=example,dc=com' (Doc ID 1336034.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Access Manager - Version: 11.1.1.3.0 and later   [Release: and later ]
Information in this document applies to any platform.

Symptoms

After upgrading  OAM 10g to OAM11g ( 11.1.1.3 ) the OIDDAS doesn't work longer.

the following exception were thrown :

11/06/20 11:13:33 [severe] thrown:
javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name 'dc=example,dc=com'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3013)
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_getAttributes(LdapCtx.java:1294)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_getAttributes(ComponentDirContext.java:213)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(PartialCompositeDirContext.java:121)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(PartialCompositeDirContext.java:109)
at javax.naming.directory.InitialDirContext.getAttributes(InitialDirContext.java:121)

Changes

upgrade OAM following the instruction of  http://download.oracle.com/docs/cd/E14571_01/upgrade.1111/e10129/upgrade_oam.htm#BAJJAHBA

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