DB2 - Problem description
Problem IC82814 | Status: Closed |
XA TRANSACTIONS THAT TIME-OUT DUE TO LONG RUNNING QUERIES MY LEAVE ORPHAN TRANSACTIONS ON THE SERVER SIDE | |
product: | |
DB2 CONNECT / DB2CONNCT / 970 - DB2 | |
Problem description: | |
XA Transactions that time-out due to long running queries my leave orphan transactions on the Server Side for the life of a physical connection and/or application. When a MSDTC trasaction times out and aborts you will send the following errors: "-99999 ERROR [24000] [IBM] CLI0115E Invalid cursor state." -998 Not in a transaction ERROR [58005] [IBM][IDS/UNIX64] SQL0998N Error occurred during transaction or heuristic processing. Reason Code = "15". Subcode = "15". In a multi-thread application with multiple active msdtc transactions. If you encounter long running queries that cause the transactions to abort. It is possible for an active query to not receive the Transaction Abort request, thus leaving the transaction active and orphaned on the server side until the associated connection is physically closed or reused elsewhere in the application. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * CLI/ADONET users with XA transactions. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7.7 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows | |
Solution | |
From DB2 v97 FP7 if CLI gets the XA errors, they will be propagated back correctly, resulting in taking the correct decisions by XA manager. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.04.2012 24.10.2012 24.10.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.7, 9.7.FP7 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.7 |