My Oracle Support Banner

Random Problems Encountered In XML Integration Steps When Running ODI 11g Scenarios Populating JMS XML Data Servers In Parallel Using The Bind Mechanism (Doc ID 1616099.1)

Last updated on MARCH 08, 2017

Applies to:

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


When executing an ODI version Specific Procedure using the bind mechanism having :

  On Source tab

    An SQL select instruction retrieving values into a single bind variable called IDVALUE

  On Target Tab

   An OdiStartScen call with following syntax :


using the bind Variable (#IDVALUE) values coming from the source tab as input values to startup Variables of a Scenario launched in Asynchronous manner which in turn calls a set of Integration Interfaces with appropriate filters to construct an XML structure which is written to a JMS XML QUEUE set up with the following URL:


the following error message is signalled

ODI-1240: Flow In VALIDITY2 002 fails while performing a Integration operation. This flow loads target table VALIDITY2.
ODI-1228: Task In VALIDITY2 002 (Integration) fails on the target JMS_QUEUE_XML connection JMSQXHRMMC_LOC.
Caused By: java.sql.SQLException: transaction rollback: serialization failure

These error message were signalled at random Integration Interfaces step in the Package. indicating a possible collision between the XML Schema.


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
   On Source tab
   On Target Tab
 Create an ODI Variable
 Modify the JMS XML Data Server URL s Parameter
 Set Up The Package
 Execute the Specific Procedure

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.