OIM 11g Error Xellerate.Database Cannot Get Connection From Datasource

(Doc ID 1342814.1)

Last updated on SEPTEMBER 29, 2017

Applies to:

Identity Manager - Version 11.1.1.3.0 and later
Information in this document applies to any platform.
**Checked for Relevance on 25-Jul-2014**

Symptoms

OIM 11g server logs show connection error messages after a new install or changes to oim-config.xml.

[2011-06-30T00:16:47.716+10:00] [oim_server1] [ERROR] [] [XELLERATE.DATABASE] [tid: ADP CLASS Watch Dog] [userId: xelsysadm] [ecid: 0000J3RkYPcFCCpLKQk3ye1E2nDL00000G,1:25216] [APP: oim#11.1.1.3.0] Class/Method: DBPoolManager/getConnection/Exception encounter some problems: Error while retrieving database connection.Please check for the following[[
Database srever is up.
DirectDB settings in configuration file are correct.
]]
[2011-06-30T00:16:47.716+10:00] [oim_server1] [ERROR] [] [XELLERATE.DATABASE] [tid: ADP CLASS Watch Dog] [userId: xelsysadm] [ecid: 0000J3RkYPcFCCpLKQk3ye1E2nDL00000G,1:25216] [APP: oim#11.1.1.3.0] Class/Method: DirectDB/getConnection encounter some problems: Error while retrieving database connection.Please check for the follwoing[[
Database srever is running.
Datasource configuration settings are correct. java.sql.SQLException: java.sql.SQLException: Exception occurred while getting connection: oracle.ucp.UniversalConnectionPoolException: Cannot get Connection from Datasource
at com.thortech.xl.util.DirectDB$DBPoolManager.getConnection(DirectDB.java:441)
at com.thortech.xl.util.DirectDB.getConnection(DirectDB.java:176)
at com.thortech.xl.dataobj.util.ADPClassWatchDog.getMaxUpdateTimestamp(ADPClassWatchDog.java:50)
at com.thortech.xl.dataobj.util.ADPClassWatchDog.run(ADPClassWatchDog.java:146)

]]
[2011-06-30T00:16:47.717+10:00] [oim_server1] [ERROR] [] [XELLERATE.ADAPTERS] [tid: ADP CLASS Watch Dog] [userId: xelsysadm] [ecid: 0000J3RkYPcFCCpLKQk3ye1E2nDL00000G,1:25216] [APP: oim#11.1.1.3.0] ADPClassWatchDog: Error occured while getting the max adp_update timestamp

Changes

OIM configuration file, oim-config.xml in the MDS doesn't have the @dburl or @dbuser parameters filled:

<directDBConfigParams driver="oracle.jdbc.OracleDriver" url="@dburl"
username="@dbuser" passwordKey="OIMSchemaPassword"
checkoutTimeout="1200" idleTimeout="360" maxCheckout="1000"
maxConnections="20" sslEnabled="false"
....



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