DB2 - Problem description
Problem IC76556 | Status: Closed |
THE INSPECT TOOL CAN LEAK MEMORY WHEN INCORRECTLY INSERTING A COMPRESSION | |
product: | |
DB2 FOR LUW / DB2FORLUW / 910 - 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: * * Persons using compression * **************************************************************** * 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 * * freed 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: * * Please upgrade to DB2 v9.1 FP11 or newer. * **************************************************************** | |
Local Fix: | |
Restart the database to free the leaked memory in DBHEAP | |
available fix packs: | |
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows | |
Solution | |
Please upgrade to DB2 v9.1 FP11 or newer. | |
Workaround | |
Restart the database to free the leaked memory in DBHEAP. | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC76771 IC76773 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.05.2011 20.12.2011 20.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.1.FP11 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.11 |