By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,924 Members | 1,651 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,924 IT Pros & Developers. It's quick & easy.

event monitor -dropped default one

P: n/a
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

Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
It's fine to drop this evmon.

Did you do this drop by actually "drop event monitor db2detaildeadlock",
or did you just delete the files? I don't think db2 cleans up the output
files on a drop event monitor, but clearly that path is gone. Remember
that there's one of these default event monitors per database...

If you used the sql statement to drop the evmon, then bounce your
system, connect to the database, and do "ps -ef | grep
DB2DETAILEDDEADLOCK". You shouldn't see any processes...if you do, then
check the catalogs (sysibm.syseventmonitors...it seems like the evmon
wasn't really dropped).

hi****@gmail.com wrote:
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

Nov 12 '05 #2

P: n/a
I dropped it from the control center. The directories in the instance
did not get cleaned. So, I manually removed them. I will bounce the
instance and see if we get error messages.

I see the db2event DB2DETAILDEADLOCK process in 'ps -ef' output, they
are tied to db2sysc.

Thanks Sean for your input.

Nov 12 '05 #3

P: n/a
If the process is there, then the evmon wasn't dropped...you can use the
SQL statement "drop event monitor' if it re-appears after restart.

hi****@gmail.com wrote:
I dropped it from the control center. The directories in the instance
did not get cleaned. So, I manually removed them. I will bounce the
instance and see if we get error messages.

I see the db2event DB2DETAILDEADLOCK process in 'ps -ef' output, they
are tied to db2sysc.

Thanks Sean for your input.

Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.