Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC66840 Status: Geschlossen

SETTING NEW TRANSACTION GIVE ERROR IN BUSY FETCHING

Produkt:
DB2 FOR LUW / DB2FORLUW / 980 - 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.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.
verfügbare FixPacks:
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

Lösung
Problem was first fixed in DB2 UDB Version 9.8 FixPack 3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.03.2010
21.12.2010
21.12.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.8.FP3
Problem behoben lt. FixList in der Version
9.8.0.3 FixList