DB2 FOR LUW / DB2FORLUW / A50 - DB2

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.

**************************************************************** 
* 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                                            * 
****************************************************************

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)

Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4)

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

06.03.2014
18.09.2014
18.09.2014