|
Problem IC83535
|
Status: Closed |
DB2DIAG.LOG ENTRIES WITHOUT A MESSAGE LEVEL CAN CAUSE A TRAP WHEN RUNNING PD_GET_DIAG_HIST |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
An entry in the db2diag.log without a LEVEL value can
cause a segmentation fault in the agent running the
PD_GET_DIAG_HIST with a stack similar to the following:
strncasecmp
_Z18sqlrwGetPDDiagHistP8sqlrr_cbP22sqlrwGetPDDiagHistArgsPPvPl
_Z30sqlrwGetWLMTableFunctionResultP8sqlrr_cbP20sqlrw_rpc_tf_requ
estPPvPl
_Z36sqlrwGetWLMTableFunctionMergedResultjPPv
_Z29sqlerTrustedRtnCallbackRouterjPPv
pd_get_diag_hist
sqloInvokeFnArgs |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of PD_GET_DIAG_HIST *
****************************************************************
* PROBLEM DESCRIPTION: *
* An entry in the db2diag.log without a LEVEL value can *
* cause a segmentation fault in the agent running the *
* PD_GET_DIAG_HIST with a stack similar to the following: *
* *
* strncasecmp *
* _Z18sqlrwGetPDDiagHistP8sqlrr_cbP22sqlrwGetPDDiagHistArgsPPv *
* Pl *
* _Z30sqlrwGetWLMTableFunctionResultP8sqlrr_cbP20sqlrw_rpc_tf_ *
* requ *
* estPPvPl *
* _Z36sqlrwGetWLMTableFunctionMergedResultjPPv *
* _Z29sqlerTrustedRtnCallbackRouterjPPv *
* pd_get_diag_hist *
* sqloInvokeFnArgs *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v10.1 FP1 or newer *
**************************************************************** |
| Local Fix: |
Removing the entries from the db2diag.log can prevent the trap. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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 |
The trap will not occur with the fix applied. |
| Workaround |
Removing the entries from the db2diag.log can prevent the trap. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.05.2012
06.11.2012
06.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
