DB2 FOR LUW / DB2FORLUW / A10 - DB2

"db2pd -alldbs -inst" can loop displaying information like this: 
 
Instance db2inst1 uses 64 bits and DB2 code release SQL10053 
with level identifier 0604010E 
Informational tokens are DB2 v10.5.0.3, s140203, IP23551, Fix 
Pack 3. 
 
Operating System Information: 
 
OSName:   Linux 
NodeName: test.ibm.com 
Version:  2 
Release:  6 
Machine:  x86_64 
Distros:  Red Hat Enterprise Linux Server 6.2 
 
 
CPU Information: 
TotalCPU    OnlineCPU   ConfigCPU   Speed(MHz)  HMTDegree 
Cores/Socket 
40          20          40          2261        1           10 
 
 
Physical Memory and Swap (Megabytes): 
TotalMem    FreeMem     AvailMem    TotalSwap   FreeSwap 
1034132     947         n/a         409600      323023 
 
Virtual Memory (Megabytes): 
Total       Reserved    Available   Free 
1443732     n/a         n/a         323969 
 
Message Queue Information: 
MsgSeg      MsgMax      MsgMap      MsgMni      MsgTql 
MsgMnb      MsgSsz 
n/a         65536       65536       1034240     65536 
65536       16 
 
Shared Memory Information: 
ShmMax               ShmMin               ShmIds      ShmSeg 
 
1084365606912        1                    258560      258560 
 
 
Semaphore Information: 
SemMap      SemMni      SemMns      SemMnu      SemMsl 
SemOpm      SemUme      SemUsz      SemVmx      SemAem 
256000      258560      256000      256000      1175000     32 
n/a         20          32767       32767 
 
CPU Load Information: 
Short     Medium    Long 
61.140000 52.210000 30.560000 
 
CPU Usage Information (percent): 
Total     Usr       Sys       Wait      Idle 
100.00000 n/a        n/a        n/a        0.000000 
 
.... 
 
db2pd can also be seeing growing in virtual memory. 
 
This problem will only occur on environments with very large 
bufferpool configurations. 
 
Note:  db2pd -alldbs -inst is also issued by db2fodc -hang 
implicitly.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1, Fixpack 5                       * 
****************************************************************

Manually kill db2pd after the data has been collected.

First fixed in DB2 Version 10.1, Fixpack 5

see Local Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

13.01.2015
14.07.2015
14.07.2015