DB2 - Problem description
Problem IC65319 | Status: Closed |
SETTING NEW TRANSACTION GIVE ERROR IN BUSY FETCHING | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Application getting error saying The DB2Command is currently busy Fetching if a result set with HOLD cursor is in the middle of reading and application try to commit and start new transaction. [ERROR] System.InvalidOperationException: The DB2Command is currently busy Fetching. at IBM.Data.DB2.DB2Command.OnSchemaChanging() at IBM.Data.DB2.DB2Command.set_Transaction(DB2Transaction value) | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 UDB Version 9.7 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error description field for more information. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.7 FixPack 2. * **************************************************************** | |
Local Fix: | |
Use separate connection for fetching with cursor hold so that the transaction works in different connection. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 2. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC66840 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.12.2009 25.05.2010 25.05.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |