suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT22976 Status: Closed

ROUTINE EXECUTION MONITORING STOPS WORKING, SPAMS DB2DIAG.LOG WITH
ALLOCRTNSTMTTABLE MESSAGE

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
When the monitoring of routine execution is enabled through the
following database configuration settings :

   Routine data                             (MON_RTN_DATA) =
BASE
   Routine executable list            (MON_RTN_EXECLIST) = ON

A faulty memory usage tracking mechanism will result in an
internal accounting limit being hit prematurely, at which point
the monitoring of routine execution will stop working, and the
db2diag.log will start being flooded with the following messages
:

FUNCTION: DB2 UDB, database monitor,
sqmRtnMetricsNode::allocRtnStmtTable, probe:10
MESSAGE : ZRC=0x8B0D000B=-1962082293=SQLM_RC_NOMEM_MONH
          "No memory available in 'Database Monitor Heap'"
          DIA8300C A memory heap error has occurred.
DATA #1 : String, 55 bytes
Unable to allocate statement routine metrics hash table

This is not a memory leak - the objects are freed as expected -
but a flawed tracking of objects that are solely for the purpose
of monitoring routine execution.  The "No Memory" message is not
because the monitor heap is truly exhausted, but due to the
internal accounting limit being encountered.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Systems with monitoring of routine execution enabled         *
* (MON_RTN_EXECLIST = ON)                                      *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 Version 11.1 Mod 4 Fix Pack 4                 *
****************************************************************
Local Fix:
Disable the monitoring of routine execution :
db2 connect to 
db2 update db cfg using mon_rtn_execlist OFF mon_rtn_data none
Solution
Workaround
see Local Fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.10.2017
06.12.2018
06.12.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)