|
Problem IC99874
|
Status: Closed |
SEVERE WLMTABLEFUNCTIONMERGED MESSAGES AGAINST RUNNING OF PD_GET_DIAG_HIST TABLE FUNCTION |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Against running of pd_get_diag_hist table function, messages
similar to following might show up in the db2diag.log :
014-01-31-08.46.07.640474-300 I2103055A591 LEVEL: Severe
PID : 11602022 TID : 72728 PROC :
db2sysc 0
INSTANCE: <inst-name> NODE : 000 DB :
<db-name>
APPHDL : 0-41858 APPID: <app>
AUTHID : <auth-id> HOSTNAME: <host-name>
EDUID : 72728 EDUNAME: db2agent (<db-name>) 0
FUNCTION: DB2 UDB, WLM, sqlrwGetWLMTableFunctionMergedResult,
probe:30
CALLED : DB2 UDB, WLM, sqlrwGetWLMTableFunctionMergedResult
RETCODE : ZRC=0x80000158=-2147483304=SQLZ_RC_SYSTEM_ERR
"Unexpected system error."
The immediate reason of these messages might be insufficient
APPLHEAPSZ.
However, it might be a result of over-committing of memory in
the box too.
The messages are for Information only and not Severe in nature
in this context. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users using pd_get_diag_hist table function *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix *
* Pack 4) or higher *
**************************************************************** |
| Local Fix: |
Tune up APPLHEAPSZ as necessary to avoid the messages.
Make sure there is no over-committing of memory in the box.
(The INSTANCE_MEMORY could be set to a fixed value in a
multiple instance, multi-partition setup to avoid over
committing of memory) |
| Solution |
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.03.2014
18.09.2014
18.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
