DB2 - Problembeschreibung
Problem IC71326 | Status: Geschlossen |
CLI ERRORS CAUSED BY EMPTY GLOBAL TRANSACTION. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
If there is an empty global transaction and you use connection pooling you will get CLI error. In a cli trace you will see "CLI0116E Invalid transaction state. SQLSTATE=25000" coming after a SQLDisconnect. Following the CLI0116E you will also get a "CLI0125E Function sequence error. SQLSTATE=HY010" Your end application is more likely to see the CLI0124E error. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * User that use empty global transactions and connection * * pooling. * **************************************************************** * PROBLEM DESCRIPTION: * * If there is an empty global transaction and you use * * connection * * pooling you will get CLI error. * * * * * * * * In a cli trace you will see "CLI0116E Invalid transaction * * * * state. SQLSTATE=25000" coming after a SQLDisconnect. * * Following * * the CLI0116E you will also get a "CLI0125E Function * * sequence * * error. SQLSTATE=HY010" * * * * * * * * Your end application is more likely to see the CLI0124E * * error. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.7 fix pack 4 or later. * **************************************************************** | |
Local-Fix: | |
Don't use an empty global transaction or don't use connection pooling. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
Fixed in DB2 v9.7 fix pack 4. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 20.09.2010 24.05.2011 24.05.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP4 | |
Problem behoben lt. FixList in der Version | |
9.7.0.4 |