JDBC Driver Does Not Support XA, Hence Cannot Be A Participant In Two-phase Commit On JCS SX
(Doc ID 2352432.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Java Cloud Service - SaaS Extension - Version N/A to N/A [Release 1.0]
Information in this document applies to any platform.
java_OPSS_wlsaas Resource Could Not be Prepared Because JDBC Driver Does Not Support XA (Global) Transactions:
You might experience issues with an instance because the java_OPSS_wlsaas resource could not be prepared.
Commencing with JCS - SaaS Extension 17.1.3, newly provisioned instances support Fusion Middleware 22.214.171.124. This support requires that JCS - SaaS Extension has an internal datasource for the OPSS policy store. This datasource is created in the JCS - SaaS Extension instance domain to support the policy store in the created schema. By default, the OPSS datasource must support the global transactions protocol as OnePhaseCommit. With this configuration, the customer might receive an error message similar to this:
Exception occurred during commit of transaction ... weblogic.transaction.RollbackException: Could not prepare resource 'java_OPSS_wlsaas
JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation,
set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = java_OPSS
This happens because the OPSS datasource doesn’t support XA Commits distributed transactions.
JDBC driver does not support XA, hence cannot be a participant in two-phase commit.
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