OID12c - DIP Log Throws Error "Failed to obtain DB connection from data source 'schedulerDS'" And Sync Between AD to OID Doesn't Work.
(Doc ID 2539488.1)
Last updated on APRIL 03, 2023
Applies to:
Oracle Internet Directory - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.1.3.0 version, Directory Integration Platform
ACTUAL BEHAVIOR
---------------
DIP is not syncing the users from AD to OID
wls_ods1-diagnostic.log file show below error messages -
2019-04-19T13:47:19.288-04:00] [wls_ods1] [ERROR] [] [org.quartz.impl.jdbcjobstore.JobStoreTX] [tid: <TID>] [userId: weblogic] [ecid: <ECID>] [APP: DIP] [partition-name: DOMAIN] [tenant-name: GLOBAL] MisfireHandler: Error handling misfires: Failed to obtain DB connection from data source 'schedulerDS': java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/schedulerDS' javax.naming.NameNotFoundException: Unable to resolve 'jdbc.schedulerDS'. Resolved 'jdbc'[[
org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'schedulerDS': java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/schedulerDS' javax.naming.NameNotFoundException: Unable to resolve 'jdbc.schedulerDS'. Resolved 'jdbc' [See nested exception: java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/schedulerDS' javax.naming.NameNotFoundException: Unable to resolve 'jdbc.schedulerDS'. Resolved 'jdbc']
at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:636)
at org.quartz.impl.jdbcjobstore.JobStoreTX.getNonManagedTXConnection(JobStoreTX.java:72)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.doRecoverMisfires(JobStoreSupport.java:3011)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:3789)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:3809)
Caused by: java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/schedulerDS' javax.naming.NameNotFoundException: Unable to resolve 'jdbc.schedulerDS'. Resolved 'jdbc'
at org.quartz.utils.JNDIConnectionProvider.getConnection(JNDIConnectionProvider.java:166)
at org.quartz.utils.DBConnectionManager.getConnection(DBConnectionManager.java:112)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:633)
... 4 more
org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'schedulerDS': java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/schedulerDS' javax.naming.NameNotFoundException: Unable to resolve 'jdbc.schedulerDS'. Resolved 'jdbc' [See nested exception: java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/schedulerDS' javax.naming.NameNotFoundException: Unable to resolve 'jdbc.schedulerDS'. Resolved 'jdbc']
at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:636)
at org.quartz.impl.jdbcjobstore.JobStoreTX.getNonManagedTXConnection(JobStoreTX.java:72)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.doRecoverMisfires(JobStoreSupport.java:3011)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:3789)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:3809)
Caused by: java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/schedulerDS' javax.naming.NameNotFoundException: Unable to resolve 'jdbc.schedulerDS'. Resolved 'jdbc'
at org.quartz.utils.JNDIConnectionProvider.getConnection(JNDIConnectionProvider.java:166)
at org.quartz.utils.DBConnectionManager.getConnection(DBConnectionManager.java:112)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:633)
... 4 more
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 |