Regression In Behaviour Of dod=true Parameter Of XML Driver URL After Upgrade To ODI 11.1.1.6.3
(Doc ID 1548910.1)
Last updated on JUNE 16, 2022
Applies to:
Oracle Data Integrator - Version 11.1.1.6.3 to 11.1.1.6.4 [Release 11gR1]Information in this document applies to any platform.
Symptoms
Consider the following complex set up of Oracle Data Integrator (ODI) Scenarios made up of:
- A Master Scenario containing:
- An Integration Interface which loads the Data from the JMS XML Queue using the parameters:
JMS_COMMIT: false
SYNCHRO_JMS_TO_XML: true
CLIENTID: #GLOBAL.<VARIABLE NAME> - Scenario 1 (OdiStartScen ASYNC) called with Variables such as #GLOBAL.<VARIABLE NAME> in a Context <CONTEXT 1>.
- Scenario 2 (OdiStartScen ASYNC) called with Variables such as #GLOBAL.<VARIABLE NAME> in a Context <CONTEXT 2>.
- OdiWaitForChild waiting for the two child Scenarios to commit.
- An Integration Interface based on "LKM JMS XML to SQL" which just runs a parameter to commit the JMS READ and purge the JMS message:
JMS_COMMIT: true
- An Integration Interface which loads the Data from the JMS XML Queue using the parameters:
- A child Scenario <SCENARIO 1> in Context <CONTEXT 1> which reads the data from the same JMS QUEUE with same CLIENTID (passed in startup Variable from Master Scenario) and write to database:
JMS_COMMIT: false
SYNCHRO_JMS_TO_XML: fa;se
CLIENTID: #GLOBAL.<VARIABLE NAME>
- A child Scenario <SCENARIO 2> in Context <CONTEXT 2> which reads the data from the same JMS QUEUE with same CLIENTID (passed in startup Variable from Master Scenario) and write to a database:
JMS_COMMIT: false
SYNCHRO_JMS_TO_XML: fa;se
CLIENTID: #GLOBAL.<VARIABLE NAME>
In the URL of JMS Queue Data Server, observe dod=true.
When executing the above set of Scenarios in ODI 10g, the expected data is propagated to the target Datastores.
After upgrade to ODI 11.1.1.6.3, and using the same set up, no data is propagated to the target Datastores.
Changes
Changed behavior between ODI 10g and ODI 11.1.1.6.3 after upgrade.
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 |