DB2 - Problem description
Problem IC65250 | Status: Closed |
COMMITTRANSACTION FAILS IF THE RESULTSET IS NOT CLOSED | |
product: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problem description: | |
A .NET application fails by committing the transaction before closing the associated result set object. The error message is: "CommitTransaction needs an open connection. The current connection status is Open, Executing." | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 UDB Version 9.1 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error description field for more information. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.1 FixPack 9. * **************************************************************** | |
Local Fix: | |
If the user can modify their application, it'll be a workaround to close the result set before committing the transaction. | |
available fix packs: | |
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.1 FixPack 9. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC65317 IC65318 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.12.2009 13.04.2010 13.04.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.1.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.9 |