home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC76378 Status: Closed

UTILHEAP MEMORY LEAK WHEN AUTOMATIC STATISTICS COLLECTION PROCESSES A TABLE
WITH A STATISTICS PROFILE WITH INDEXES

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
A leak to UTILHEAP occurs when automatic statistics collection 
processes a table with a statistics profile if the problem 
specifies the collection of index statistics. 
 
The leak might affect any database operations that require 
UTILHEAP. 
 
The leak can be observed with db2pd -memblocks option.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.5 Fix Pack 9 or later                      * 
****************************************************************
Local Fix:
Unset the profile, which leads automatic statistics collection 
to use default statistics options.
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 V9.5 Fix Pack 9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC80356 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.05.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 FixList