DB2 - Problem description
Problem IT19533 | Status: Closed |
SIGNIFICANT INCREASE IN SHARED APPLICATION HEAP AFTER UPGRADE TO10.5 FOR QUERIES REFERENCING RANGE PARTITIONED TABLES | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
In DB2 10.5 release number of object metrics available for monitoring was extended, which results in slightly higher dynamic section size for compiled SQLs. Difference is insignificant unless given query references table containing very high number of tables or, more likely, tables containing multiple partitions (>1000) because the metrics are maintained for each object separately. This increase will be exposed even more significantly in environments with high paralelism level (INTRA_PARALLEL=YES). Allocations will be shown in: $ db2pd -db <db_name> -memblocks appl top 20 output with "File" ID 1127556507, e.g: PoolID PoolName TotalSize(Bytes) %Bytes TotalCount . LOC File 20 appshrh 8068968184 50.16 4803 . 1592 1127556507 20 appshrh 6946287888 43.18 4260 . 1729 1127556507 20 appshrh 379804896 2.36 6489 . 1515 1127556507 20 appshrh 136376208 0.85 8874 . 5146 1095929873 20 appshrh 16798208 0.10 3052 . 739 1234005865 This APAR will address this behavior and reduce memory footprint for such SQLs. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 11.1 Mod 2 Fix Pack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.03.2017 23.06.2017 23.06.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |