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

THE INSPECT TOOL CAN LEAK MEMORY WHEN INCORRECTLY INSERTING A COMPRESSION
DICTIONARY

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The DB2 INSPECT ROWCOMPESTIMATE option estimates the 
effectiveness of row compression for a table. It can leak memory 
when the compression dictionary was built successfully but 
attempting to insert it into table didn't succeed or complete. 
For such case, the dictionary should be free'ed from the memory. 
 The most common situation for this is when INSPECT 
ROWCOMPESTIMATE runs against a table that does not support data 
row compression.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of the INSPECT utility                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The DB2 INSPECT ROWCOMPESTIMATE option estimates the         * 
* effectiveness of row compression for a table. It can leak    * 
* memory                                                       * 
* when the compression dictionary was built successfully but   * 
* attempting to insert it into table didn't succeed or         * 
* complete.                                                    * 
* For such case, the dictionary should be free'ed from the     * 
* memory.                                                      * 
* The most common situation for this is when INSPECT           * 
* ROWCOMPESTIMATE runs against a table that does not support   * 
* data                                                         * 
* row compression.                                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 FP5 or newer                             * 
****************************************************************
Local Fix:
Restart the database to free the leaked memory in DBHEAP
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
Upgrade to DB2 v9.7 FP5 or newer
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.06.2011
20.12.2011
20.12.2011
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