My Oracle Support Banner

"Invalid string or buffer length" when Running an ODI 11g Interface from ODI Studio which Loads Data from Excel (Doc ID 2582790.1)

Last updated on SEPTEMBER 03, 2019

Applies to:

Oracle Data Integrator - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Symptoms

When attempting to move data from an Excel spreadsheet to the Oracle Database and using an ODI standalone agent fails with the following error message:

[2019-08-21T17:32:42.701+02:00] [] [NOTIFICATION:16] [ODI-1125] [] [tid: <TID>] [ecid: <ECID>] Agent <AGENT_NAME> started session <SESSION_NAME> (<ID>) from scenario <SCENARIO_NAME> in work repository <REP_NAME> using context GLOBAL.
[2019-08-21T17:32:43.190+02:00] [] [NOTIFICATION:16] [ODI-1101] [] [tid: <TID>] [ecid: <ECID>] Agent <AGENT_NAME> successfully completed session <SESSION_NAME> (<ID>) (for scenario <SCENARIO_NAME>) on <REP_NAME> using context GLOBAL with statistics: Rows 1984 Inserts 0 Updates 0 Deletes 1984 Errors 0.
[2019-08-21T17:33:05.406+02:00] [] [NOTIFICATION:16] [ODI-1125] [] [tid: <TID>] [ecid: <ECID>] Agent <AGENT_NAME> started session <SESSION_NAME> (<ID>) from scenario <SCENARIO_NAME> in work repository <REP_NAME> using context GLOBAL.
[2019-08-21T17:33:05.833+02:00] [] [WARNING] [ODI-1134] [] [tid: <TID>] [ecid: <ECID>] Agent <AGENT_NAME> encountered an error: ODI-1226: Step <STEP_NAME> fails after 1 attempt(s).
[2019-08-21T17:33:05.834+02:00] [] [ERROR] [ODI-1217] [] [tid: <TID>] [ecid: <ECID>] Session <SESSION_NAME> (<ID>) fails with return code 8000.[[
ODI-1226: Step xxxxxxx fails after 1 attempt(s).
ODI-1240: Flow xxxxxxx fails while performing a Loading operation. This flow loads target table <TABLE_NAME>.
Caused By: java.sql.SQLException: [Microsoft][ODBC Driver Manager] Invalid string or buffer length
at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6957)
at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7114)
at sun.jdbc.odbc.JdbcOdbc.SQLGetDataString(JdbcOdbc.java:3907)
at sun.jdbc.odbc.JdbcOdbcResultSet.getDataString(JdbcOdbcResultSet.java:5698)
at sun.jdbc.odbc.JdbcOdbcResultSet.getString(JdbcOdbcResultSet.java:354)
at sun.jdbc.odbc.JdbcOdbcResultSet.getObject(JdbcOdbcResultSet.java:1678)
at oracle.odi.query.typemapping.PassThroughReader.getValue(PassThroughReader.java:28)
at oracle.odi.query.JDBCTemplate.getValue(JDBCTemplate.java:209)
at oracle.odi.runtime.agent.execution.sql.concurrent.FastJDBCRecordSet.call(FastJDBCRecordSet.java:143)
at oracle.odi.runtime.agent.execution.sql.concurrent.FastJDBCRecordSet.call(FastJDBCRecordSet.java:1)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)


In the agent log, errors like below can be seen:

[2019-08-21T18:24:39.810+02:00] [] [ERROR] [ODI-1131] [] [tid: <TID>] [ecid: <ECID>] Agent <AGENT_NAME> encountered an error: ODI-1503: Load plan logs for instance <INSTANCE_NAME>, run 1 are corrupted: Could not find session '<SESSION_NAME>' (for step '<STEP_NAME>').[[
ODI-1503: Load plan logs for instance <INSTANCE_NAME>, run 1 are corrupted: Could not find session '<SESSION_NAME>' (for step '<STEP_NAME>').
at oracle.odi.runtime.agent.loadplan.RepositoryUtil.throwDataConsistencyException(RepositoryUtil.java:2640)
at oracle.odi.runtime.agent.loadplan.RepositoryUtil.logScenStepCompleted(RepositoryUtil.java:1069)

[2019-08-21T18:24:39.696+02:00] [odi] [ERROR] [] [oracle.odi.agent] [tid: <TID>] [ecid: <ECID>] ODI-1503: Load plan logs for instance <INSTANCE_NAME>, run 1 are corrupted: Could not find session '<SESSION_NAME>' (for step '<STEP_NAME>').[[
at oracle.odi.runtime.agent.loadplan.RepositoryUtil.throwDataConsistencyException(RepositoryUtil.java:2640)
at oracle.odi.runtime.agent.loadplan.RepositoryUtil.logScenStepCompleted(RepositoryUtil.java:1069)

Changes

 The interfaces were working fine for several years, but started failing after the agent was restarted.

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


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