Transaction Handling In BRM JCA Adapter 7.4 And Later : No More XA Transaction ?
Last updated on FEBRUARY 27, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
The <document 1535198.1> (Transaction Mode of BRM JCA Adapter for Communications Pre Built Integrations) conveys that LOCAL_TRANSACTION should be used. Oracle is suggesting that XA Transaction should not be used anymore.
Please clarify the reasoning and implications.
The above note is for below symptoms:
1. Transactional issue happening under certain race conditions
2. Transaction getting rolled back on BRM even though everything would seem fine from AIA
Below are few questions in this context :
1) Is this true (to use only LOCAL_TRANSACTION) for both 7.4 and 7.5?
2) What is the implication when one changes the transaction mode from XA to LOCAL_TRANSACTION?
a. It seems like that LOCAL_TRANSACTION just means it is not XA anymore, so it will also cause data sync issues.
b. Don’t understand how this will fix race conditions? It will be just faster, is that it?
c. Would this lead to data sync issues? (e.g. BRM commits fine but AIA rolls back)
d. If so, instead of #2 symptoms, it will be the same thing as transaction getting committed on BRM even though everything rolls back from AIA.
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