DB2 FOR LUW / DB2FORLUW / A10 - DB2

The PD_LOG_GET_MSGS routine returns the messages recorded in the 
DB2 notify log.  As the notify log grows in size, calling the 
PD_LOG_GET_MSGS allocates a larger portion of memory, up to a 
limit of 20% of the INSTANCE_MEMORY setting.  This amount of 
memory can be excessive and may either fail to be allocated or 
strain memory resources on the server.  A failure will appears 
as follows in the db2diag.log, though it is possible to receive 
a similar failure executing other routines (Examine the failing 
statement or investigate the SQL statement cache to determine if 
the PD_LOG_GET_MSGS routine is being executed on the server): 
 
EDUID   : 123                  EDUNAME: db2agent (SAMPLE) 0 
 
FUNCTION: DB2 UDB, WLM, sqlrwExpandableBuffer::addElement, 
probe:10 
CALLED  : DB2 UDB, WLM, sqlrwExpandableBuffer::addElement 
 
RETCODE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH 
 
          "No memory available in 'Application Heap'" 
 
          DIA8301C No memory available in the application heap. 
 
Referencing the sysibmadm.pdlogmsgs_last24hours table function 
may also trigger the high memory allocation.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 systems are affected                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5                       * 
****************************************************************

Manage the size of the db2 notify log as follows: 
1. On UNIX, archive (or remove) the DB2 notify log ( <db2 
instance>.nfy in the DIAGPATH directory ).  On Windows, archive 
(or clear) the application event log. 
2. Manage the size/contents of the DB2 notify log using the 
DIAGSIZE and/or NOTIFYLEVEL settings.

Problem first fixed in DB2 Version 10.1 Fix Pack 5

see Local Fix

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

18.11.2014
23.07.2015
23.07.2015