DB2 FOR LUW / DB2FORLUW / 970 - DB2

In some rare circumstances the PD_GET_DIAG_HIST() table function 
may become stuck looping without making any progress giving the 
outward 
appearance of a hang. This can leave sessions that cannot be 
forced from the DBMS. 
 
Operating system tools like top will show db2sysc process 
consuming up to 100% CPU. 
Using 'db2pd -edus' will reveal a single thread/EDU consuming 
most/all CPU time within the db2sysc process. 
 
A db2trc of this EDU will show it is looping in the following 
two functions: 
 
 pdDiagGetNextRecordFromBuffer 
 pdDiagReadFromFileIntoBufferBS

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 Fix Pack 9                        * 
****************************************************************

Truncate the current db2diag.log file by executing '> 
db2diag.log'. This will break the loop and result in SQL1042C 
being returned by the EDU.

DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in DB2 version 9.7 Fix Pack 9

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC97386 IC97389 
Nachfolger : 

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

14.03.2013
16.12.2013
16.12.2013

9.7.FP9