|
Problem IC76771
|
Status: Closed |
THE INSPECT TOOL CAN LEAK MEMORY WHEN INCORRECTLY INSERTING A COMPRESSION DICTIONARY |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - 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 INSPECT ROWCOMPESTIMATE *
****************************************************************
* 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.5 FP9 or newer *
**************************************************************** |
| Local Fix: |
Restart the database to free the leaked memory in DBHEAP |
| available fix packs: |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Memory is no longer leaked in DB2 v9.5 FP9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.06.2011
12.03.2012
12.03.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.9
|
 |
