|
Problem IT36140
|
Status: Closed |
PERFORMANCE IMPACTS WITH HUGE AMOUNT OF ROW LOCKS
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
Querying or modifying millions of sequential table records may
result in unexpected long response times.
The used hashing algorithm for the internal lock handling leads
to an anomaly in the locklist size ranges.
Some ranges, e.g locklist is between 2097121 and 2097152, may
increase the response time of such a transaction significantly. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* AIX/Linux *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2 v11.5.6.0 *
**************************************************************** |
| Local Fix: |
Use LOCK TABLE statement to avoid the need to acquire large
number of row locks
or
Use a fixed locklist of a "good" size |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* AIX/Linux *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2 v11.5.6.0 *
**************************************************************** |
| Comment |
fix in db2 v11.5.6.0 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.03.2021
09.06.2021
09.06.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
