DB2 FOR LUW / DB2FORLUW / 970 - DB2

The process memory map collection performed on Solaris during 
the db2pd -stack command has been improved in version 9.5 Fix 
Pack 6 and version 9.7 Fix Pack 2.  It is no longer triggering 
severe hang symptoms. 
However, it still may take a relatively long time (eg. 30 
seconds on some symptoms), and causes some contention with other 
memory operations on the DB2 server. 
 
Since it is intrusive and may lead to misleading diagnostics, it 
will be removed from the diagnostics collected in db2pd -stack. 
The information is rarely needed, and can be collected by the 
native Solaris pmap <process> command, which is much quicker and 
less intrusive.  The pmap command will be added to the db2fodc 
-perf and -hang data collections.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2/Solaris systems                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5 to retain diagnostic   * 
* capability of db2pd -stack                                   * 
****************************************************************

When the db2pd -stack command is required, it is recommended to 
substitute the following: 
db2pd -latches 
pstack <db2sysc process ID> 
pmap <db2sysc process ID> 
 
If running db2fodc -perf or -hang, modify the appropriate 
sqllib/bin/db2cos_hang or db2cos_perf scripts to use the 
alternate commands.

Problem first fixed in DB2 Version 9.7 Fix Pack 5

see Local Fix

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

16.12.2010
02.05.2012
02.05.2012

9.7.FP5