home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC63767 Status: Geschlossen

INADEQUATE ERROR MESSAGE WHEN TRANSACTIONTIMEOUT IS REACHED WHILE
READING ROWS VIA IFXDATAREADER

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Error when TransactionTimeout is reached while reading rows via 
IfxDataReader 
 -99999 ERROR [24000] [IBM] CLI0115E  Invalid cursor state. 
SQLSTATE=24000 
The error message is misleading and hard to catch because it 
does not point to the problem. 
Customer expects an error message which is related to the cause 
of the problem. 
After catching an error the application has to take the 
appropriate action. 
This is not possible when the error message does not point to 
the problem.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* INADEQUATE ERROR MESSAGE WHEN TRANSACTIONTIMEOUT IS          * 
* REACHEDWHILE READING ROWS VIA IFXDATAREADERError when        * 
* TransactionTimeout is reached while reading                  * 
* rowsviaIfxDataReader-99999 ERROR [24000] [IBM] CLI0115E      * 
* Invalid cursor state.SQLSTATE=24000The error message is      * 
* misleading and hard to catch because itdoes not point to the * 
* problem.Customer expects an error message which is related   * 
* to thecauseof the problem.After catching an error the        * 
* application has to take theappropriate action.This is not    * 
* possible when the error message does not pointtothe problem. * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to IBM Data Server Provider for .Net 9.7 Fix Pack 3  * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in Version 9.7 Fix Pack 3   This fix 
should be applied on the client.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC69931 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
15.10.2009
11.11.2010
11.11.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList