java.sql.SQLException

ODI-40768: Could not save the file /tmp/customer-0-0.xml because a class java.sql.SQLException occurred and said: java.sql.SQLException: java.sql.SQLException: incompatible data type in conversion: from SQL type NUMERIC to java.lang.Integer, value: 3782511387

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web17302

  • via Oracle Community by user775218, 1 year ago
    ODI-40768: Could not save the file /tmp/customer-0-0.xml because a class java.sql.SQLException occurred and said: java.sql.SQLException: java.sql.SQLException: incompatible data type in conversion: from SQL type NUMERIC to java.lang.Integer, value: 3782511387
  • ODI-40768: Could not save the file C:\tmp\XML_xx_EXPORT_166201111.xml because a class java.sql.SQLException occurred and said: java.sql.SQLException: java.sql.SQLException: Numeerinen ylivuoto
  • via Oracle Community by kmoso, 1 year ago
    Could not save the file D:\ODI\oracledi\XMLFiles\Cuentas11g.xml because a class java.sql.SQLException occurred and said: java.sql.SQLException: java.sql.SQLException: Wrong data type: type: <b>NUMERIC (2) expected: INTEGER value: 301000000232</b>
  • Stack trace

    • java.sql.SQLException: ODI-40768: Could not save the file /tmp/customer-0-0.xml because a class java.sql.SQLException occurred and said: java.sql.SQLException: java.sql.SQLException: incompatible data type in conversion: from SQL type NUMERIC to java.lang.Integer, value: 3782511387 at com.sunopsis.jdbc.driver.xml.SnpsXmlFile.writeToFile(SnpsXmlFile.java:751) at com.sunopsis.jdbc.driver.xml.SnpsXmlConnection.internalExecute(SnpsXmlConnection.java:769) at com.sunopsis.jdbc.driver.xml.SnpsXmlPreparedStatement.execute(SnpsXmlPreparedStatement.java:46) at oracle.odi.runtime.agent.execution.sql.SQLCommand.execute(SQLCommand.java:166) at oracle.odi.runtime.agent.execution.sql.SQLExecutor.execute(SQLExecutor.java:102) at oracle.odi.runtime.agent.execution.sql.SQLExecutor.execute(SQLExecutor.java:1) at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50) at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2906) at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2609) at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:540) at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:453) at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1740) at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1596) at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:582) at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:214) at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:513) at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1070) at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:123) at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:83) at java.lang.Thread.run(Thread.java:662)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago