Unexpected transaction errors and rollback when Database Adapter is driving multiple emulated data-sources to make updates to the same schema
(Doc ID 1326689.1)
Last updated on APRIL 19, 2021
Applies to:Oracle SOA Suite - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
You have an installation of Oracle Application Server 10g Release 3 (101.3.x) where you are running BPEL processes that leverage the Database Adapter to read and update data located in a single schema. For this scenario to apply, you have created multiple Emulated XA DataSource definitions, each with a different data-source name and JNDI location, but all accessing the same database location and schema.
At run-time, you intermittently encounter errors similar to the following in the OPMN log file (located under $ORACLE_HOME/opmn/logs) for the OC4J container where the BPEL Process Manager is running:
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