|
Problem IT10715
|
Status: Closed |
PD_GET_DIAG_HIST DOES NOT RESPOND TO FORCE REQUEST. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
PD_GET_DIAG_HIST table function does not respond to a force
request. This APAR will change that behavior and will allow to
force an application executing it.
DB2 EDU processing PD_GET_DIAG_HIST function can be identified
by a thread stack similar to this one:
pdDiagGetNextLogRecord
pdDiagGetNextRecordFromBuffer
pdDiagGetNextRecord
PADiagLogCollEngn::getNextRows
sqlrwGetPDDiagHist
sqlrwGetWLMTableFunctionResult
sqlrwGetWLMTableFunctionMergedResult
sqlerTrustedRtnCallbackRouter
pd_get_diag_hist |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.5 Fix Pack 7 or higher. *
**************************************************************** |
| Local Fix: |
n/a |
| Solution |
Problem first fixed in DB2 version 10.5 Fix Pack 7. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.08.2015
28.01.2016
28.01.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
