|
Problem IC66840
|
Status: Closed |
SETTING NEW TRANSACTION GIVE ERROR IN BUSY FETCHING |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - 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.8 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error description field for more information. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.8 FixPack 3. *
**************************************************************** |
| Local Fix: |
Use separate connection for fetching with cursor hold so that
the transaction works in different connection. |
| available fix packs: |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
Problem was first fixed in DB2 UDB Version 9.8 FixPack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.03.2010
21.12.2010
21.12.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.3
|
 |
