DB2 - Problem description
Problem IC80545 | Status: Closed |
WHEN "DB2PD -MEMBLOCK PID=AAA" DOESN'T IST ALL MEMORY BLOCKS IN PRIVATE MEMORY ON HP, AND IT MAY HANG ON SUN | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
when "db2pd -memblock pid=aaa" doesn't ist all memory blocks in private memory on HP, and it may hang on SUN 1. when run db2pd -memb pid=xxx, it hang on SUN in pdScrapeAndPrint when it fails on pdProcGetData ( to read proc map ) 2. db2pd -memb pid=xxx, doesn't list all memory blocks in private memory on HP. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 on Solaris and HP-UX. * **************************************************************** * PROBLEM DESCRIPTION: * * when "db2pd -memblock pid=aaa" doesn't ist all memory blocks * * in private memory on HP, and it may hang on SUN * * * * 1. when run db2pd -memb pid=xxx, it hang on SUN in * * pdScrapeAndPrint when it fails on pdProcGetData ( to read * * proc map ) * * * * 2. db2pd -memb pid=xxx, doesn't list all memory blocks in * * private memory on HP. * **************************************************************** * RECOMMENDATION: * * Update to db2 version 9.5 fixpack 9 or later fixpacks. * **************************************************************** | |
Local Fix: | |
n/a | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
This problem is first fixed in db2 version 9.5 fixpack 9. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC80750 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.12.2011 07.03.2012 07.03.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.9 |