| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC90716 | Status: Closed |
IN SOME RARE CIRCUMSTANCES THE PD_GET_DIAG_HIST() TABLE FUNCTION MAY HANG. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - 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.1 FixPack 3. * **************************************************************** | |
| 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 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
First fixed in DB2 Version 10.1 FixPack 3. | |
| Workaround | |
not known / see Local fix | |
| BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC90859 follow-up : | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.03.2013 27.09.2013 27.09.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 |
|
| 10.1.0.3 |
|
| 10.1.0.4 |
|