Common Errors with XML

Detect the errors coming from XML

Errors appear often in Oracle Data Integrator in the following way:

java.sql.SQLException: No suitable driver
at ...
at ...
...

the java.sql.SQLException code simply indicates that a query was made through the JDBC driver, which has returned an error. This error is frequently a database or driver error, and must be interpreted in this direction.

Only the part of text in bold must first be taken in account. It must be searched in the XML driver documentation. If its contains a specific error code, like here, the error can be immediately identified.

If such an error is identified in the execution log, it is necessary to analyze the SQL code send to the database to find the source of the error. The code is displayed in the description tab of the task in error.

The most common errors with XML are detailed below, with their principal causes.

Common Errors

Connection Errors

No suitable driver

The Oracle Data Integrator Driver for XML is not correctly installed.

Errors in the interfaces

File <XML file> is already locked by another instance of the XML driver.

The XML file is locked by another user/application. Close all application that might be using the XML file. If such an application has crashed, then remove the .lck file remaining in the XML file's directory.

The DTD file "xxxxxxx.dtd" doesn't exist

This exception may occur when trying to load an XML file by the command LOAD FILE. The error message can have two causes:

• The path of the DTD file is incorrect.

• The corresponding XML file was already opened by another schema (during connection for instance).

Table not found: S0002 Table not found: <table name> in statement [<SQL statement>]

The table you are trying to access does not exist in the schema.

Column not found: S0022 Column not found: <column name> in statement [<SQL statement>]

The column you are trying to access does not exist in the tables specified in the statement.