|
Problem IC64011
|
Status: Closed |
MEMORY LEAK IN IBM OLEDB PROVIDER USING OPTIMISTIC LOCKING OPTION. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
While opening and closing recorded sets using the same
connection a memory leak is witnessed on DB2 client side.
This only while using the IBM OLEDB provider with OPTIMISTIC
LOCKING option. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Windows users *
****************************************************************
* PROBLEM DESCRIPTION: *
* While opening and closing recorded sets using the same *
* connection a memory leak is witnessed on DB2 client side. *
* This only while using the IBM OLEDB provider with OPTIMISTIC *
* LOCKING option. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fixpak 1 *
**************************************************************** |
| Local Fix: |
Use ODBC driver or IBM.NET provider or when possible don't use
Optimistic Locking option. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
Use ODBC driver or IBM.NET provider or when possible don't use
Optimistic Locking option. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.10.2009
08.03.2010
08.03.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
