DB2 - Problem description
Problem IT41469 | Status: Closed |
Sortheap memory leak possible for index-and access on MDC tables | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
Multidimensional Clustering Tables (MDC) can be access by Index - Anding using a Block Index in one leg of the IXAND operator and a Row ID (regular) Index on the other leg of the access. Ref see : https://www.ibm.com/docs/en/db2/11.5?topic=tables-block-indexes When this happens, it is possible that a memory leak occurs in the shared sortheap. This is difficult to identify: the only external symptom is usually a large amount of allocated memory blocks in the shared sortheap memory pool, without any real activity on the system. e.g. the output may look like: Database Member 0 -- Database SAMPLE -- Active -- Up 0 days 01:05:36 -- Date 2022-06-15-15.33.32.678781 Address MemSet PoolName Id SecondId Overhead LogSz LogHWM PhySz PhyHWM CfgSize Bnd BlkCnt CfgParm 0x00007FED105462F8 DB-SAMPLE shsorth 18 0 0 4227162856 5030019072 4999610368 5030019072 38958268416 No 24017920 SHEAPTHRES_SHR Db2 Support can further examine the data to determine the source of the allocations. This can eventually lead to error SQL0955 when other sort consumers can no longer obtain sufficient sort memory. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users who are using MDC * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade DB2 to 11.5.8 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users who are using MDC * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade DB2 to 11.5.8 * **************************************************************** | |
Comment | |
First fixed in DB2 Version 11.5.8 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.07.2022 14.09.2022 14.09.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |