OID 11g DIP Log Error: DIP-10599 / [LDAP: error code 53 - Function Not Implemented] Or: DIP-10581 / javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]

(Doc ID 2304799.1)

Last updated on SEPTEMBER 06, 2017

Applies to:

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

Symptoms

Oracle Internet Directory (OID) 11g Directory Integration Platform (DIP).

Using DIP, e.g., to create synchronization profile, fails with DIP log error:

[2017-09-05T15:14:57.086-04:00] [wls_ods1] [ERROR] [DIP-10599] [oracle.dip] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: <ECID number>] [APP: DIP#11.1.1.2.0] Errors encountered while starting Directory Integration Platform Scheduler : {0}[[
javax.naming.OperationNotSupportedException: [LDAP: error code 53 - Function Not Implemented]; remaining name 'cn=Server Configs,cn=Directory Integration Platform,cn=Products,cn=OracleContext'

And/Or,

RuntimeException log error:

[2008-11-21T00:11:10.915-08:00] [wls_ods] [ERROR] [] [org.quartz.impl.jdbcjobstore.JobStoreTX] [tid: 25] [userId: <anonymous>][ecid: <ECID number>] [APP: DIP] ClusterManager: Error managing cluster: Failed to obtain DB connection from data source 'schedulerDS': java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/schedulerDS' java.sql.SQLException: Cannot obtain connection: driverURL = jdbc:weblogic:pool:schedulerDS, props = {EmulateTwoPhaseCommit=false, connectionPoolID=schedulerDS, jdbcTxDataSource=true, LoggingLastResource=false, dataSourceName=schedulerDS}.[[
Nested Exception: java.lang.RuntimeException: Failed to setAutoCommit to true for pool connection

AuthenticationException while connecting to OID:

[2008-11-21T00:12:08.812-08:00] [wls_ods] [ERROR] [DIP-10581] [oracle.dip] [tid: 11] [userId: <anonymous>] [ecid: <ECID number>] [APP: DIP] DIP was not able to get the context with the given details {0}[[
javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]

 

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