How Can We 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 NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo - Version 11.1.1.2.0 and later
Information 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

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