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

APAR status

• Closed as program error.

Error 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.
  

Local fix

• Disable the monitoring of routine execution :
  db2 connect to <database>
  db2 update db cfg using mon_rtn_execlist OFF mon_rtn_data none
  

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

Problem conclusion

• Problem first fixed in DB2 Version 11.1 Mod 4 Fix Pack 4
  

Temporary fix

• see Local Fix
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• sqm
  

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• RB10 PSN

     UP