ODI Jobs Failing With "ORA-12519, TNS:no Appropriate Service Handler Found"
(Doc ID 2507109.1)
Last updated on OCTOBER 18, 2019
Applies to:
Oracle Data Integrator - Version 11.1.1.9.0 and laterInformation in this document applies to any platform.
Symptoms
Oracle Data Integrator (ODI) executions are failing intermittently with "ORA-12519, TNS:no appropriate service handler found" error:
...[ERROR] [ODI-1134] [] [<TID>] [<ECID>] Agent localagent encountered an error: ODI-1217: Session <NAME> (<SESSION ID>) fails with return code 8000.
Caused by: ODI-1226: Step <NAME> fails after 1 attempt(s).
[[
ODI-1217: Session <NAME> (<SESSION ID>) fails with return code 8000.
ODI-1226: Step <NAME> fails after 1 attempt(s).
ODI-1240: Flow <NAME> fails while performing a Integration operation. This flow loads target table null.
ODI-1228: Task <NAME> fails on the target ORACLE connection <CONNECTION NAME>.
Caused By: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12519, TNS:no appropriate service handler found
at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.doGetConnection(LoginTimeoutDatasourceAdapter.java:133)
at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.getConnection(LoginTimeoutDatasourceAdapter.java:62)
at oracle.odi.core.datasource.dwgobject.support.OnConnectOnDisconnectDataSourceAdapter.getConnection(OnConnectOnDisconnectDataSourceAdapter.java:74)
at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:113)
at com.sunopsis.sql.SnpsConnection.createConnection(SnpsConnection.java:390)
at com.sunopsis.sql.SnpsConnection.connect(SnpsConnection.java:348)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.getExecutor(SnpSessTaskSql.java:2962)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2901)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:577)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:468)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2128)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1930)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:580)
at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:513)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1073)
at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
at java.lang.Thread.run(Thread.java:662)
Changes
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 |
Changes |
Cause |
Solution |
References |