DB2 - Problem description
Problem IC62752 | Status: Closed |
PERFORMANCE ISSUE OF CLOSE FOR UR/CS CURSORS WHEN 'WITH RELEASE' IS SPECIFIED | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
If "WITH RELEASE" is specified on a CLOSE of a cursor opened with isolation UR or CS (or equivalently if SQL_ATTR_CLOSE_BEHAVIOR is set to SQL_CC_RELEASE for a UR or CS isolation cursor), the close cursor processing may be delayed if the transaction holds many locks. With the change introduced in this APAR, the performance of such a close (with RELEASE) will improve and will not be sensitive to the number of locks held by the transaction. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * applications using UR cursors and closing 'with release' * **************************************************************** * PROBLEM DESCRIPTION: * * close cursor performs slowly if WITH RELEASE is specified * **************************************************************** * RECOMMENDATION: * * move to DB2 for LUW V97fp1 * **************************************************************** | |
Local Fix: | |
Do not specify RELEASE behaviour for CLOSE of CS or UR cursors | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Fixed in DB2 for LUW V97 fp1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.08.2009 17.02.2010 17.02.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP1 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |