DB2 - Problembeschreibung
Problem IC65319 | Status: Geschlossen |
SETTING NEW TRANSACTION GIVE ERROR IN BUSY FETCHING | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 2. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC66840 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 23.12.2009 25.05.2010 25.05.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP2 | |
Problem behoben lt. FixList in der Version | |
9.7.0.2 |