My Oracle Support Banner

ODI JMS XML Integration Interface or Mapping Failing With Invalid Schema Name (Doc ID 1982431.1)

Last updated on MARCH 04, 2019

Applies to:

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

Symptoms

NOTE: In the examples below, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo instance). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

 

 

The following message is received when running a Mapping (or Integration interface) for loading XML or JMS XML data, and using the default, in Memory engine for XML:

...
Caused By: java.sql.SQLException: invalid schema name: REFERENCEDATAVERYLONGSCHEMANAME1
 at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
 at org.hsqldb.jdbc.JDBCStatement.fetchResult(Unknown Source)
 at org.hsqldb.jdbc.JDBCStatement.executeQuery(Unknown Source)
 at com.sunopsis.jdbc.driver.xml.SnpsXmlStatementRedirector.executeQuery(SnpsXmlStatementRedirector.java:126)
 at com.sunopsis.jdbc.driver.xml.SnpsXmlStatement.executeQuery(SnpsXmlStatement.java:49)
 at com.sunopsis.jdbc.driver.JMSXMLStatement.executeQuery(JMSXMLStatement.java:232)
 at oracle.odi.query.JDBCTemplate.executeQuery(JDBCTemplate.java:196)
 at oracle.odi.query.JDBCTemplate.executeQuery(JDBCTemplate.java:204)
 at oracle.odi.runtime.agent.execution.sql.SQLDataProvider.readData(SQLDataProvider.java:100)
 at oracle.odi.runtime.agent.execution.sql.SQLDataProvider.readData(SQLDataProvider.java:38)
 at oracle.odi.runtime.agent.execution.Executor.handleDataMovementTask(Executor.java:309)
 at ...
Caused by: org.hsqldb.HsqlException: invalid schema name: REFERENCEDATAVERYLONGSCHEMANAME1
 at org.hsqldb.error.Error.error(Unknown Source)
 at org.hsqldb.SchemaManager.getSchemaHsqlName(Unknown Source)
 at org.hsqldb.SchemaManager.getSchemaName(Unknown Source)
 at org.hsqldb.Session.getSchemaName(Unknown Source)
 at org.hsqldb.SchemaManager.getTable(Unknown Source)
 at org.hsqldb.ParserDQL.readTableName(Unknown Source)
 at org.hsqldb.ParserDQL.readTableOrSubquery(Unknown Source)
 at org.hsqldb.ParserDQL.XreadTableReference(Unknown Source)
 at org.hsqldb.ParserDQL.XreadFromClause(Unknown Source)
 at org.hsqldb.ParserDQL.XreadTableExpression(Unknown Source)
 at org.hsqldb.ParserDQL.XreadQuerySpecification(Unknown Source)
 at org.hsqldb.ParserDQL.XreadSimpleTable(Unknown Source)
 at org.hsqldb.ParserDQL.XreadQueryPrimary(Unknown Source)
 at org.hsqldb.ParserDQL.XreadQueryTerm(Unknown Source)
 at org.hsqldb.ParserDQL.XreadQueryExpressionBody(Unknown Source)
 at org.hsqldb.ParserDQL.XreadQueryExpression(Unknown Source)
 at org.hsqldb.ParserDQL.compileCursorSpecification(Unknown Source)
 at org.hsqldb.ParserCommand.compilePart(Unknown Source)
 at org.hsqldb.ParserCommand.compileStatements(Unknown Source)
 at org.hsqldb.Session.executeDirectStatement(Unknown Source)
 at org.hsqldb.Session.execute(Unknown Source)
 ... 25 more

Note the URL used in the definition of XML / JMS XML Data Server has the schema name ("s" parameter) set to:

...&s=referenceDataVeryLongSchemaName1&dod=true...

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


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