I dropped the db2detaildeadlock event monitor without flushing the
events that were full hoping dropping it will clear the messages also.
I now understand this is a default monitor that I should not dropped.
Now there are "SEVERE" error messages occuring everyday -few times.
What should I do to ensure these messages are not thrown.
2005-04-27-06.24.04.087962-240 I6572370C334 LEVEL: Warning
PID : 17042 TID : 1 PROC : db2event
(DB2DETAILDEADLOCK)
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, database monitor, sqm___sqlmeiot, probe:7
MESSAGE : target type 0 failed to open DB2DETAILDEADLOCK with rc
-2079522804
2005-04-27-06.24.04.089540-240 I6572705C403 LEVEL: Severe
PID : 109914 TID : 1 PROC : db2agent (
SAMPLE)
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-301 APPID: *LOCAL.db2inst1.050427102435
FUNCTION: DB2 UDB, database monitor, sqm___start_evmon, probe:40
RETCODE : ZRC=0x840D000C=-2079522804=SQLM_RC_EVIO2 "path not found"
2005-04-27-06.24.04.090680-240 I6573109C458 LEVEL: Severe
PID : 109914 TID : 1 PROC : db2agent (
SAMPLE)
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-301 APPID: *LOCAL.db2inst1.050427102435
MESSAGE : event monitor name
DATA #1 : Hexdump, 17 bytes
0x2003E988 : 4442 3244 4554 4149 4C44 4541 444C 4F43
DB2DETAILDEADLOC
0x2003E998 : 4B K
Thanks,
SK