DB2 FOR LUW / DB2FORLUW / 970 - DB2

Following SQLO_NOMEM_MONH error from sqm_object::new(), the 
instance traps with signal # 11 in function 
sqm_evmon_entity::adjust_table_event().  You will see following 
entry or similar in the db2diag.log: 
 
2010-07-07-21.21.03.238318-240 I14243400A509      LEVEL: Severe 
PID     : XXXX                    TID  : 1           PROC : 
db2evmli(XXXX) 
 
INSTANCE: XXXX                NODE : 000         DB   : XXXX 
APPHDL  : XXXXX                APPID: XXXXXXXXXXXXXXXXXXXX 
AUTHID  : XXXXX 
FUNCTION: DB2 UDB, database monitor, sqm_object::new, probe:100 
RETCODE : ZRC=0x8B0F000B=-1961951221=SQLO_NOMEM_MONH 
          "No memory available in 'Database Monitor Heap'" 
          DIA8300C A memory heap error has occurred. 
 
You will see stack similar to the following in the trap file for 
the trapping event monitor process: 
 
      sqm_evmon_entity::adjust_table_event + 0x80 
      sqm_evmon::write_event + 0x6e0 
      sqm_evmon::flush_tab_event + 0x520 
      sqm_evmon::gen_db_exit_events + 0x720 
      sqmEvmonWriter::cleanupEvmonWriter + 0x1520 
      sqmEvmonWriter::evmonWriter + 0x3d0 
      sqleIndCoordProcessRequest + 0x9c0 
      sqleRunAgent + 0x710 
      sqloCreateEDU + 0x690 
      sqloRunGDSv + 0x4a0 
      sqloInitEDUServices + 0xd40 
      sqloSystemControllerMainjPFivEPFviEPPvPi + 0xe30 
      sqloRunInstance + 0x2d0 
      DB2main + 0xee0 
      main + 0x30 
      main_opd_entry + 0x50

USERS AFFECTED: 
=============== 
Customer using version 9.1 and above on all platforms. 
 
PROBLEM DESCRIPTION: 
==================== 
Instance will trap after receiving SQLO_NOMEM_MONH. This error 
can be seen in the db2diag.log right before the trap 
information. The trap file in the DIAGPATH will show that the 
process/thread is trapping in the following function: 
 
sqm_evmon_entity::adjust_table_event 
 
RECOMMENDATION: 
=============== 
Increase the monitor heap size, which will avoid the 
SQLO_NOMEM_MONH error. This will avoid the error handling code 
path causing the trap.

Increasing the monitor heap size will reduce the chances or 
completely avoid the instance crash.

DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem is first fixed in version 9.7 Fixpack 4.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

15.09.2010
03.05.2011
03.05.2011

9.7.FP4