DB2 - Problem description
Problem IC63179 | Status: Closed |
An attempt to create an incorrectly huge memory pool is not proh ibited. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When an incorrectly huge memory pool is asked, DB2 attempts to create it rather than returning an error. This can lead to an exhaustion in the memory resource in the box. This problem occurs only in a rare event, where the DB2 component needing a memory pool incorrectly calculates the amount they need. So far, the only known such scenario is when runstats was run with quantiles and freqvalues values more than twenty thousand. n/a n/a | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL. However, so far, the symptom is only seen by those * * running RUNSTATS command with very large (e.g. over 20,000) * * quantiles and/or freqvalues. * **************************************************************** * PROBLEM DESCRIPTION: * * Same as ERROR DESCRIPTION * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 9.5 Fix pack 5 or later. * **************************************************************** | |
Local Fix: | |
Refrain from running runstats with very high freqvalues and quantiles. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 9.5 Fix pack 5. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.09.2009 21.02.2010 21.02.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |