OID 11.1.1.7 Startup Fails During Configuration Script Config.sh. Out Log File Errors: oracle.as.config.ProvisionException: OID-23663 | [LDAP: error code 53 - Super user name can not be the DN of an existing entry.]

(Doc ID 2013434.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Internet Directory - Version 11.1.1.7.0 and later
Oracle Fusion Middleware - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Symptoms

Oracle Internet Directory (OID) 11.1.1.7.

OID startup fails during configuration script ($MW_HOME/Oracle_IDM1/bin/config.sh):

Error creating ASComponent oid1.
Cause:
An internal operation has failed: Failed to start the component

The install<date_time>.out file shows:

...<snip>...
oracle.as.config.ProvisionException: OID-23663
at oracle.iam.management.oid.install.wls.OIDComponentHelper.setSuperUserCredentials(OIDComponentHelper.java:2248)
at oracle.iam.management.oid.install.wls.OIDComponent.postCreateConfig(OIDComponent.java:349)
at oracle.as.provisioning.fmwadmin.ASComponentProv.createComponent(ASComponentProv.java:145)
...<etc>...
Caused by: oracle.ldap.util.UtilException: NamingException encountered in ldapModify [LDAP: error code 53 - Super user name can not be the DN of an existing entry.]
at oracle.ldap.util.Util.ldapModify(Util.java:2555)
at oracle.iam.management.oid.install.wls.OIDComponentHelper.setSuperUserCredentials(OIDComponentHelper.java:2229)
... 19 more
...<etc>...
Instance asinst_1 already exists, continuing with component creation
/u01/app/Oracle/Middleware/Oracle_IDM1  /u01/app/Oracle/Middleware/asinst_1  asinst_1
oracle.as.config.ProvisionException: Failed to start the component
at oracle.as.provisioning.fmwadmin.ASComponentProv.createComponent(ASComponentProv.java:157)
at oracle.as.provisioning.fmwadmin.ASComponentProv.createComponent(ASComponentProv.java:73)
at oracle.as.provisioning.fmwadmin.ASInstanceProv._createComponent(ASInstanceProv.java:401)
...<etc>...
oracle.as.provisioning.util.ConfigException:
Error creating ASComponent oid1.
Cause:
An internal operation has failed: Failed to start the component
Action:
See logs for more details.
at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
at oracle.as.provisioning.fmwadmin.ASInstanceProv._createComponent(ASInstanceProv.java:414)
at oracle.as.provisioning.fmwadmin.ASInstanceProv.createComponent(ASInstanceProv.java:358)
...<etc>...
Caused by: oracle.as.config.ProvisionException: Failed to start the component
at oracle.as.provisioning.fmwadmin.ASComponentProv.createComponent(ASComponentProv.java:157)
at oracle.as.provisioning.fmwadmin.ASComponentProv.createComponent(ASComponentProv.java:73)
at oracle.as.provisioning.fmwadmin.ASInstanceProv._createComponent(ASInstanceProv.java:401)
... 15 more

...<end>...


Previous installations and configurations were successfully done on other OID nodes, using the same procedures, same realm namespace, RCU version, etc.

Changes

Applied an OID Bundle Patch.

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