Isolation Level with XA Transactions can be Tightly or Loosely Coupled with XATransLoose Property (Doc ID 1669131.1)

Last updated on MARCH 08, 2017

Applies to:

JDBC - Version 11.1.0.7 and later
Information in this document applies to any platform.

Symptoms

A JDBC application peforms an XA transaction using 2 XA data sources.
  One XA data source uses an isolation level of Serialized.  
  The other XA data source uses an isolation level of Read Committed.


If the 2 data sources are pointing to 2 different databases then the 2nd data source behaves as expected. ( the second transaction can see changes from the the first transaction )
If the 2 data sources are pointing to 2 different schemas but on the same database then the 2nd XA data source behaves as if it is Serialized instead of Read Committed. ( the second transaction cannot see changes from the the first transaction ) .

Changes

 Different transaction isolation behavior depending on whether the two XA connections are from different databases or from the same database.

Cause

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