My Oracle Support Banner

ODI 12c "ODI-26039: Connection failed" and "NumberFormatException" Error when Loading Very Large Integer from XML (Doc ID 2333605.1)

Last updated on OCTOBER 29, 2018

Applies to:

Oracle Data Integrator - Version 12.2.1.1.0 to 12.2.1.3.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

In Oracle Data Integrator (ODI) 12.2.1.1, attempting to test a connection to an XML file that contains a long integer results in the following error:

ODI-26039: Connection failed.
java.sql.SQLException: class java.sql.SQLException
java.lang.NumberFormatException: For input string: "9223372036854775808"
  at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.doGetConnection(LoginTimeoutDatasourceAdapter.java:144)
  at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.getConnection(LoginTimeoutDatasourceAdapter.java:73)
  at com.sunopsis.sql.SnpsConnection.testConnection(SnpsConnection.java:1258)
  ...
Caused by: java.sql.SQLException: class java.sql.SQLException
java.lang.NumberFormatException: For input string: "9223372036854775808"
  at com.sunopsis.jdbc.driver.xml.SnpsXmlFile.readDocument(SnpsXmlFile.java:508)
  at com.sunopsis.jdbc.driver.xml.SnpsXmlFile.readDocument(SnpsXmlFile.java:536)
  at com.sunopsis.jdbc.driver.xml.SnpsXmlFile.synchronizeFromFile(SnpsXmlFile.java:705)
  at com.sunopsis.jdbc.driver.xml.SnpsXmlFile.(SnpsXmlFile.java:125)
  ...
Caused by: java.sql.SQLException: java.lang.NumberFormatException: For input string: "9223372036854775808"
  at com.sunopsis.jdbc.driver.xml.data.AbstractXmlLoader.loadFile(AbstractXmlLoader.java:213)
  at com.sunopsis.jdbc.driver.xml.SnpsXmlFile.readDocument(SnpsXmlFile.java:503)
  ... 20 more
Caused by: java.lang.NumberFormatException: For input string: "9223372036854775808"
  at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
  at java.lang.Long.parseLong(Long.java:596)
  at java.lang.Long.valueOf(Long.java:803)
  at com.sunopsis.jdbc.driver.xml.data.XmlDataTranslatorDefault.convertXmlStringToValue(XmlDataTranslatorDefault.java:83)
  at oracle.odi.jdbc.driver.xml.model.xmlmodel.data.OdiXmlLoader.convertXmlStringToValue(OdiXmlLoader.java:481)
  at com.sunopsis.jdbc.driver.xml.data.AbstractXmlLoader.handleEndElement(AbstractXmlLoader.java:123)
  at oracle.odi.jdbc.driver.xml.model.xmlmodel.data.OdiXmlLoader.endElement(OdiXmlLoader.java:130)
  at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1679)
  at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:471)
  at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:417)
  at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:249)
  at oracle.odi.jdbc.driver.xml.io.impl.XmlFileInputPipelineStage.provideInput(XmlFileInputPipelineStage.java:38)
  at oracle.odi.jdbc.driver.xml.io.impl.XmlFileInputPipeline.doProcess(XmlFileInputPipeline.java:36)
  at com.sunopsis.jdbc.driver.xml.data.AbstractXmlLoader.loadFile(AbstractXmlLoader.java:206)
  ... 21 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
 Workaround
 A. Add or edit the XSD file to use the DECIMAL type
 B. Update the ODI components
References


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