|
Problem IC97389
|
Status: Closed |
IN SOME RARE CIRCUMSTANCES THE PD_GET_DIAG_HIST() TABLE FUNCTION MAY HANG. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.5 FixPack 4 *
**************************************************************** |
| Local Fix: |
Truncate the current db2diag.log file by executing '>
db2diag.log'. This will break the loop and result in SQL1042C
being returned by the EDU. |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 version 10.5 FixPack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.11.2013
09.09.2014
09.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
