How to Avoid The Next DB2 xa_start() Failing With Error -9 (XAER_OUTSIDE) After Than A Transaction Reaches the Timeout And Generated xa_end() with Return Code -4(XAER_NOTA)?
(Doc ID 2037890.1)
Last updated on SEPTEMBER 09, 2024
Applies to:
Oracle Tuxedo - Version 11.1.1.2.0 and laterInformation in this document applies to any platform.
Goal
Why the error -4 (XA_NOTA) during a xa_start generates a global mis-behavior for all following calls on DB2 server?
Solution
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
Goal |
Solution |
References |