My Oracle Support Banner

OID DIP Server Started but Quartz Scheduler and MBeans are Down. Configuration settings are unavailable. Directory Integration Platform is not able to get the context with the given details DIP-10013, Exception or LDAP: error code 49 - Invalid Credentials (Doc ID 1397413.1)

Last updated on JANUARY 27, 2020

Applies to:

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

Symptoms

Oracle Internet Directory (OID) with Directory Integration Platform (DIP) Server is started but Quartz Scheduler and MBeans are down.

Enterprise manager (EM) Fusion Middleware (FMW) Control console > DIP menu > Administration -> Provisioning Profiles may show error:

Configuration settings are unavailable. The profile management interfaces for the target /Farm_<DOMAIN>/<DOMAIN>/wls_ods1/DIP(11.1.1.2.0) are currently unavailable.

Clicking the "Test connection" button can return the following error:

The connection test could not be performed.
The test aborted with the message : Unable to locate the DIP Sync profile mbean - :oracle.idm.integration.sync.config:*:
Unable to locate the DIP Sync profile mbean - :oracle.idm.integration.sync.config:*:

DOMAIN_HOME is properly set to the installation (e.g., DOMAIN_HOME=/<PATH>/user_projects/domains/<DOMAIN>).


On 11.1.1.9 and higher version, WebLogic Server (WLS) Managed Server logs (wls_ods1.log) may not be specific and just have an empty Exception such as:

[2016-08-10T16:37:56.938-04:00] [wls_ods1] [ERROR] [] [oracle.dip] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: <ecid string>][APP: DIP#11.1.1.2.0] Connection to LDAP server failed - Check configuration of DIP server.
[2016-08-10T16:37:56.938-04:00] [wls_ods1] [ERROR] [] [oracle.dip] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: <ecid string>] [APP: DIP#11.1.1.2.0] Directory Integration Platform is not able to get the context with the given details : OID host: <OID_HOSTNAME> Port: <OID_SSLPORT> SSL mode:1.
[2016-08-10T16:37:56.939-04:00] [wls_ods1] [ERROR] [DIP-10013] [oracle.dip] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: <ecid string>] [APP: DIP#11.1.1.2.0] Exception
[2016-08-10T16:37:56.953-04:00] [wls_ods1] [NOTIFICATION] [EVENT_NOT_ENABLED] [oracle.dip] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: <ecid string>] [APP: DIP#11.1.1.2.0]


Older 11g versions logs may show:

[APP: DIP#11.1.1.2.0] Connection to LDAP server failed - Check configuration of DIP server.
[2011-12-21T03:13:17.206+00:00] [wls_ods3] [ERROR] [] [oracle.dip] [tid: SyncProfileMBean] [userId: weblogic] [ecid: <ecid string>] [APP: DIP#11.1.1.2.0] Directory Integration Platform is not able to get the context with the given details : OID host: <OID_HOSTNAME> Port: <OID_SSLPORT> SSL mode:1.
[2011-12-21T03:13:17.206+00:00] [wls_ods3] [ERROR] [DIP-10013] [oracle.dip] [tid: SyncProfileMBean] [userId: weblogic] [ecid: <ecid string>] [APP: DIP#11.1.1.2.0] Exception[[
javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3041)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2987)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2789)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2703)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:293)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)

And an OID ldap server log with debug trace (level 8193) shows:

[2011-12-16T16:34:44+00:00] [OID] [TRACE:16] [] [OIDLDAPD] [host: <HOSTNAME>] [pid: <PID>] [tid: <TID>] [ecid: <ECID>] ServerWorker (REG):[[
BEGIN
ConnID:0 mesgID:1 OpID:0 OpName:bind ConnIP:::ffff:<IP Address> ConnDN:Anonymous
INFO : gslfbidbDoBind * Version=3 BIND dn="cn=odisrv,cn=Registered Instances,cn=Directory Integration Platform,cn=products,cn=oraclecontext" method=128
ConnId = 0, op=0, IpAddr=::ffff:<IP Address>
2011-12-16T16:34:44 * INFO:gsleswrASndResult OPtime=4091 micro sec RESULT=49 tag=97 nentries=0
END

 

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


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