home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC71246 Status: Geschlossen

INSTANCE CRASHES IN SQM_EVMON_ENTITY::ADJUST_TABLE_EVENT() FOLLOWING
SQLO_NOMEM_MONH ERROR IN DB2DIAG.LOG

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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
Problem-Zusammenfassung:
USERS AFFECTED: 
=============== 
All users on version 9 and above. 
 
PROBLEM DESCRIPTION: 
==================== 
. 
If out of memory error is received while creating a new 
monitoring object through sqm_object::new(), it can crash the 
db2 instance. User may see SQLO_NOMEM_MONH error in the 
db2diag.log log and sqm_evmon_entity::adjust_table_event 
function in the trap file. 
 
RECOMMENDATION: 
=============== 
Increasing the monitor heap should reduce the probablity of the 
crash.
Local-Fix:
Increasing the monitor heap size will reduce the chances or 
completely avoid the instance crash.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem is first fixed in version 9.5 Fixpack 8.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
15.09.2010
21.07.2011
21.07.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP8
Problem behoben lt. FixList in der Version
9.5.0.8 FixList