|
Problem IT06476
|
Status: Closed |
DB2PD -ALLDBS -INST CAN LOOP CONTINUOUSLY ON SYSTEMS WITH VERY LARGE BUFFERPOOL CONFIGURATIONS |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
"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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5, Fix Pack 7 *
**************************************************************** |
| Local Fix: |
Manually kill db2pd after the data has been collected. |
| Solution |
First fixed in DB2 Version 10.5, Fix Pack 7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.01.2015
29.01.2016
29.01.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
