(Doc ID 463918.1)
Last updated on JANUARY 30, 2022
Applies to:Oracle Services for Microsoft Transaction Server - Version 10.2.0.1 to 188.8.131.52 [Release 10.2 to 11.2]
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)
This setting was introduced by the fix for <Bug:5410059> to control whether a new connection is always used to perform an abort or if the original connection that was enlisted could be used to perform the abort whenever possible (synchronous or asynchronous abort).
1) <Bug 4768819> was filed because certain apps would sees a slow rollback. The behavior at that time was that OraMTS would always asynchronously use a new connection to perform the abort. The fix was to allow the use of the existing connection if it was still around and still attached to the transaction. This effectively changed the behavior from ORAMTS_ABORT_MODE_NEW_CONN_ONLY to ORAMTS_ABORT_MODE_ORIG_CONN_OK, although the setting did not actually exist at that point.
2) As a result of the fix for bug 4768819, it was noted that in certain race conditions this could cause partially committed transactions. As such, via <Bug 5410059>, the ORAMTS_ABORT_MODE registry setting was added, to allow apps to revert back to the behaviour previous to bug 4768819. The default is still ORAMTS_ABORT_MODE_ORIG_CONN_OK, but apps can now revert to pre-4768819 behaviour via setting ORAMTS_ABORT_MODE_NEW_CONN_ONLY.
Anyone using Oracle Services for Microsoft Transaction Server.
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