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

DB2READER.CLOSE() IS NOT CLOSING THE UNDERLYING CURSOR, CAN HOLD DATABASE
LOCKS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The DB2 .NET Data provider's DB2Reader.Close() operation is not 
closing the underlying cursor on the database server.  It is 
possible that a cursor can hold a database lock.   Calling 
DB2Reader.Close() may not actually release that lock.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows users using DB2 .NET provider                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The DB2 .NET Data provider's DB2Reader.Close() operation is  * 
* not closing the underlying cursor on the database server.    * 
* It is possible that a cursor can hold a database lock.       * 
* Calling DB2Reader.Close() may not actually release that      * 
* lock.                                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7, Fixpack 5                        * 
****************************************************************
Local Fix:
The cursor will be released when a call to DB2Command.Dispose() 
is issued.  If the parent DB2Command object from which the 
DB2Reader object was created from is disposed, then the cursor 
will be closed, and all underlying locks held by the cursor will 
be released as well.
available fix packs:
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
First fixed in DB2 Version 9.7, Fixpack 5
Workaround
The cursor will be released when a call to DB2Command.Dispose() 
is issued.  If the parent DB2Command object from which the 
DB2Reader object was created from is disposed, then the cursor 
will be closed, and all underlying locks held by the cursor will 
be released as well.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.03.2011
21.12.2011
21.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList