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 IC84436 Status: Closed

CLI0129E RETURNED FROM A DB2 .NET Entity Framework APPLICATION

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
At the time of Connection.Close the DB2 .NET driver ensures the 
statements are freed. Looks like unfortunately Microsoft Entity 
Framework (EF) holds the ownership of the Command objects until 
it closes the connection.  This can result in a CLI0129E error. 
 
CLI0129E  An attempt to allocate a handle failed because there 
are no more handles to allocate. 
 
The DB2 driver will not be able to free statement handles when 
EF keeps the ownership of the command 
object associated with the statement handles. The real problem 
is with Microsoft Entity Framework (EF). 
 
Since the application still wants to keep such a high number of 
updates within a transaction, IBM can provide a possible 
workaround. It is by freeing up some of the statement handles 
associated with the command object that is not yet come for 
disposal. 
 
The real fix should come from Microsoft Entity Framework
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 users on Windows OS                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fix Pack 1 or higher                    * 
****************************************************************
Local Fix:
Try to minimize the number of statements within a single 
transaction.  That should reduce the number of statement handles 
and sections required by the DB2 driver.
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 V10.1 Fix Pack 1
Workaround
Try to minimize the number of statements within a single 
transaction.  That should reduce the number of statement handles 
and sections required by the DB2 driver.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
06.11.2012
06.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList