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

ERROR SQL2312N EXECUTING 'RUNSTATS INDEXES ALL' AGAINST VERY LAR
GE TABLE HAVING PARTITIONED INDEXES WHICH HEAPSIZE EXCEEDS 5242

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Whenever the memory reservation computation for runstats local 
indexes exceed 524288 pages, customers will get SQL2312N error 
suggesting the new value to be set. E.g. 
 
SQL2312N  Statistics heap size is too small to carry out the 
operation. 
Suggested heap size is "644578" pages. 
 
In customer scenario they have created table having 2943 range 
partitions and a few partitioned indexes defined on it. They 
received sql2312n when tried the following runstats command 
 
 db2 "RUNSTATS ON TABLE "CCDB"."CLAIM_COMMON"  FOR INDEXES 
CCDB"."NEW_IDX_NYT2" allow write access" 
SQL2312N  Statistics heap size is too small to carry out the 
operation. 
Suggested heap size is "644578" pages. 
 
The above problem is encountered only when partitioned indexes 
exist, runstats works fine on non-partitioned indexes.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using Runstats index all                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error description above                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 FP5 or latest                     * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fix in DB2 Version 9.7 FP 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.05.2011
17.01.2012
17.01.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList