Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC91747 Status: Closed

DUMP 'DB2PD -DPSDBCD' DATA AND 'DB2PD -DPSPRCB' DATA BY
'DB2FODC-HANG' COMMAND

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
For some 'hang' issues, the 'db2pd -dpsdbcd' data and the 'db2pd 
-dpsprcb' data is necessary for root cause analysis. However, 
currently it's not collected by 'db2fodc -hang' command. 
 
By applying this APAR, 'db2fodc -hang' command will dump the 
'db2pd -dpsdbcd' data and the 'db2pd -dpsprcb' data as part of 
the default behaviors.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 FixPack 3                            * 
****************************************************************
Local Fix:
Copy $HOME/sqllib/bin/db2cos_hang to $HOME/sqllib/adm/, and 
manually add  "db2pd -dpsdbcd" and  "db2pd -dpsprcb" into it.
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.1 FixPack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2013
17.10.2013
17.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList