Vijay,
There is an event monitor that monitors deadlocks that is on by default.
There is a directory where the deadlock event monitor files are written, 20
I think. Find that directory and delete or move all of the files but the
latest one. Alternately, you could drop then recreate that monitor stating
a larger number of files or you may decide you do not need this instance to
track deadlocks and delete it altogether.
You decide.
Hope this helps.
Paul
<vijay.db@gmail.comwrote in message
news:1171985257.402150.55790@k78g2000cwa.googlegro ups.com...
Quote:
Hi group,
>
Have a problem with event monitor so my db2diag.log is getting filled
like any thing..
>
Running DB2 V8.1 Fixpack 6 in AIX server.
>
Created a event monitor and redirecting it's output to a file..getting
error like
>
2007-02-20-00.06.52.470942 Instance:***** Node:000
PID:1229054(db2agent (*****) 0) TID:1 Appid:*LOCAL.*****.
0209B0000649
database monitor sqm___start_evmon Probe:32 Database:*****
>
DIA0001E An internal error occurred. Report the following error code :
"ZRC=0x840D000C".
>
PID:1229054 TID:1 Node:000 Title: event monitor name
0x20066B38 : 4445 4144 4C4F 434B 5F45 5654 53 DEADLOCK_EVTS
>
PID:1229054 TID:1 Node:000 Title: event monitor target
0x20066B60 : 2F68 6F6D 652F 6475 6D66 6370 312F 6D66 /home/dum/mf
0x20066B70 : 6330 3170 312F 6475 6D66 6370 312F 4E4F c/dum/NO
0x20066B80 : 4445 3030 3030 2F53 514C 3030 3030 312F DE0000/
SQL00001/
0x20066B90 : 6462 3265 7665 6E74 2F44 4C4F 434B 53 db2event/
DLOCKS
>
2007-02-20-00.06.52.500447 Instance:dumfcp1 Node:000
PID:1229054(db2agent (*****) 0) TID:1 Appid:*LOCAL.*****.
0209B0000649
database monitor sqm___evmgr::log_ev_err Probe:1 Database:*****
>
DiagData
0x2FF1B410 : 0x840D000C ....
>
As I got repeated error like this, I turned off the event monitor, but
still my db2diag.log is getting filled with the above error message?
>
Queries:
>
Is it problem with starting the event monitor?
problem with redirecting the data to file?
some other issue?
>
Thanks in advance..
vj_dba
>
