DB2 - Problem description
Problem IC77830 | Status: Closed |
CREATE INDEX WITH STATS COLLECTION ON GLOBAL TEMP TABLE OR RANGE PARTITIONED TABLE LEAKS UTILHEAP MEMORY | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
The following is an example testcase for the memory leak on a declared global temporary table : declare global temporary table session.mytemp like sysibm.syscolumns ; create index session.idx1 on session.mytemp ( name ) collect sampled detailed statistics; drop table session.mytemp; The following is an example testcase for the memory leak on a range partitioned table : create table IC.r (c1 int, c2 int) partition by range (c1) (starting (1) ending (10), ending (20)); create index IC.i on IC.r ( c2 ) collect sampled detailed statistics; The leak can be shown by examining the output from : db2pd -db dbname -memb all | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.5 Fix Pack 9 or later * **************************************************************** | |
Local Fix: | |
Instead of collecting statistics during index creation, collect statistics with a RUNSTATS command after creating the index. | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB2 V9.5 Fix Pack 9 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.07.2011 31.10.2012 31.10.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.9 |