|
Problem IC64263
|
Status: Closed |
SETTING NEW TRANSACTION GIVE ERROR IN BUSY FETCHING |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - 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.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error description field for more information. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.1 FixPack 9. *
**************************************************************** |
| Local Fix: |
Use separate connection for fetching with cursor hold so that
the transaction works in different connection. |
| available fix packs: |
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 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: IC65316 IC65319
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.10.2009
15.04.2010
15.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
|
 |
