home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC71326 Status: Closed

CLI ERRORS CAUSED BY EMPTY GLOBAL TRANSACTION.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
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.
Problem Summary:
**************************************************************** 
* 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.
available fix packs:
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

Solution
Fixed in DB2 v9.7 fix pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.09.2010
24.05.2011
24.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList