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 IC94549 Status: Closed

RUNSTATS WITH SAMPLED DETAILED INDEXES ON PARTITIONED, MDC TABLE MIGHT
RESULT IN EXCESSIVE MEMORY UTILIZATION AND SQL0973N ERROR

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Running sampled detailed index statistics on a partitioned MDC 
index might result in excessive memory utilization.  For 
example, consider a range partitioned, mdc table defined as 
follows: 
 
CREATE TABLE MDC_TEST (A INT, B INT, C INT, D INT) PARTITION BY 
RANGE (A) (STARTING 1 ENDING 500 EVERY 10) ORGANIZE BY (B,C); 
 
Three partitioned block indexes will be automatically created 
and if the statistics heap or application memory is not large 
enough, a RUNSTATS collecting sampled detailed index statistics 
could fail, producing the following error: 
 
RUNSTATS ON TABLE MDC_TEST AND SAMPLED DETAILED INDEXES ALL 
SQL0973N  Not enough storage is available in the "STAT_HEAP_SZ" 
heap or stack to process the statement.  SQLSTATE=57011 
 
Starting in DB2 10.1, the SAMPLED DETAILED option is the default 
when collecting detailed index statistics, so the following 
could fail as well: 
RUNSTATS ON TABLE MDC_TEST AND DETAILED INDEXES ALL
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 and Fix Pack 4 or higher.        * 
****************************************************************
Local Fix:
You can avoid the error by increasing the STAT_HEAP_SZ limit. 
If this is set to automatic, which is the default value, then it 
increases as needed until either the APPL_MEMORY limit is 
reached, or the INSTANCE_MEMORY limit is reached, so you can try 
increasing those values, if applicable.  If increasing the 
appropriate memory limit is not possible, you can avoid the 
problem by not collecting detailed index statistics or disable 
sampling by specifying the UNSAMPLED clause explicitly.
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 version 10.1 and Fix Pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.08.2013
02.06.2014
02.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList