Last updated on AUGUST 14, 2013
Applies to:
Oracle ESB - Version 10.1.3.4.0 and laterOracle(R) BPEL Process Manager - Version 10.1.3.4 and later
Information in this document applies to any platform.
***Checked for relevance on 08-March-2012***
Goal
You have configured an adapter with both XA (global transaction) and non-XA (local transaction) data sources. But you have some questions.
- Is this allowed?
- Which data source does the adapter use? Is there a default?
- Suppose you have the following scenario:
You have a BPEL process which invokes a database adapter with both XA and non-XA data sources defined. The adapter writes to a database table. The next activity in your process calls an Oracle Applications adapter (again with XA and non-XA data sources defined) which calls a stored procedure and throws an error. After the error, on checking the database table which was written to by the database adapter, you find the record is still there.
The transaction should have rolled back and should not have committed the write to the table, correct?
- You have configured a database adapter which you use to call a PLSQL procedure in Oracle E-Business Suite 12.0.4, but you consistently receive the following error on the invoke: ORA-02089 'Commit Is Not Allowed In A Subordinate Session'. What's the problem? Is there a workaround?
Solution
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms