DB2 - Problem description
Problem IC70866 | Status: Closed |
IN DPF ENVIRONMENT, REDISTRIBUTE COMMAND MAY HANG DUE TO MEMORY LEAK IN DYNAMIC MEMORY HEAP | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
In DPF environment, redistribute command may hang on Redistribute process monitor thread on co-ordinator agent. This happens due to memory leak on one or few of the data node. db2diag.log shows Dynamic Memory Heap error. db2diag.log shows : 2010-08-26-08.47.05.312330-300 I10157787E823 LEVEL: Error PID : 8 TID : 12345 PROC : db2sysc 10 INSTANCE: bculinux NODE : 010 DB : BCUDB APPHDL : 0-70 APPID: *N0.DB2.************* AUTHID : BCULINUX EDUID : 12345 EDUNAME: db2agntp (BCUDB) 10 FUNCTION: DB2 UDB, database utilities - Redistribute, sqlurCSourceTargetPartition::zInitRedist, probe:1253 MESSAGE : ZRC=0x8BB00005=-1951399931=SQLUC_DUHM_OUT_OF_MEM "DHM Out of memory." DIA8327C No memory available in the utility heap. DATA #1 : RDSTID, PD_TYPE_RDSTID, 41 bytes RDSTID: C.62.20100826074630.0|81(0;1550)| DATA #2 : File name, 18 bytes sqlurSTPartition.C DATA #3 : String, 39 bytes Error creating DHM consumer for DR task DATA #4 : signed integer, 4 bytes 6048 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All using Redistribute command. * **************************************************************** * PROBLEM DESCRIPTION: * * See APAR description * **************************************************************** * RECOMMENDATION: * * Upgrade to IBM DB2 v9.7 Fixpack 4 * **************************************************************** | |
Local Fix: | |
force redistribute command application handle and reissue the redistribute command with continue option. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
See APAR text | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 31.08.2010 27.05.2011 27.05.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |