DB2 - Problem description
Problem IC97925 | Status: Closed |
DB2CAT LEAKS MEMORY FOR EACH TABLE PROCESSED | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
db2cat leaks a small amount of memory for each table processed. On a database with a very large number of tables, it is possible to encounter a user data memory limit - such as the default 128MB limit on AIX. Upon hitting this limit, db2cat will fail with an error similar to the following : 13180: Unable to allocate memory for packed descriptor: len = 2608. The memory leak has no impact other than causing the db2cat program to fail. The amount of memory leaked is not excessive - on an example system 30000 tables were processed before hitting the 128MB memory limit - and the memory is released as soon as the db2cat program fails. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All systems * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * As this command is typically run in isolated problem * * diagnostic situations, it is recommended to use the * * identified workaround * **************************************************************** | |
Local Fix: | |
Increase the user data limit in the environment where the db2cat program is to be run. | |
available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB2 Version 10.5 Fix pack 4 | |
Workaround | |
see Local Fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.11.2013 22.09.2014 22.09.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.4 |