IC63179: An attempt to create an incorrectly huge memory pool is not proh ibited.

DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error 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
  

Local fix

• Refrain from running runstats with very high freqvalues and
  quantiles.
  

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.                      *
  ****************************************************************
  

Problem conclusion

• First fixed in DB2 9.5 Fix pack 5.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IZ43772

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• R950 PSY

     UP