Hello List,

My db2 is reporting "Event monitor has reached its file capacity.
ZRC=0x800D002B" in my db2diag.log file. But I havent started any event monitoring.

I was wondering, what is this related to. I'm running 8.1 for Aix.

Any help?

May be somebody else started it? An event monitor also can be defined to start automatically upon database startup.

Do:

select evmonname, autostart, target from syscat.eventmonitors;

This will give you the list of defined monitors, along with their autostart flag ('Y' means it starts automatically), and directories where their output goes.

You can then check each monitor's status by:

values (event_mon_state('<monitor name, case sensitive>'));

1 means the corresponding monitor is active.

Deactivate it by:

set event monitor <monitor name> state 0;

Hello,

Thanks for your answer.

I ran your given statement against the database and see the following event in the system:

db2detaildeadlock event:

I was wondering, If the above is a system required event? If no, can i disable this?


Thanks,

All event monitors are user-defined, so you can drop it if you want. However, deadlock monitor should not have any significant effect on database performance while providing useful data in case you experience occasional deadlocks. If you can ensure that there's enough disk space for its log you should probably leave it running.

Thanks for your answer.

How can I drop it? can i run a delete statement against the syscat.eventmonitors table?

Yes you can; it will fail however.

Look for the "DROP" statement in the SQL reference manual.

db2 => select evmonname, autostart from syscat.eventmonitors

EVMONNAME
AUTOSTART
---------------------------------------------------------------------------
DB2DETAILDEADLOCK Y

db2 => set event monitor db2detaildeadlock state 0

SQL1615W The specified event monitor is already in the requested state. SQLSTATE=01598


I'm trying to disable this event. anytime I run the above statement. It says, Its in the requested (disable) mode. But when i query the eventmonitors view. It says, its in autostart "Y" mode.

Should I assume, the above event is still active based on Autostart mode or there' something i'm not understanding.

Any suggestions?

Autostart flag tells the database manager to activate the monitor at startup. However, since its log file is full (as indicated by the message in db2diag.log) the monitor gets deactivated and when you try to deactivate it manually it is already "in the requested state".

Is it possible to alter the evetmonitor from autostart Y to N

Sathyaram

I don't think so - you'll have to drop and re-create the monitor

I think this event monitor is created by DB2 itself!!! I have seen this earlier on one of our NT server where I was getting the same message in diag log and upon investigation I found out about the existence of this event monitor with exact same name. Nobody in our shop knows how to do this and at the end I dropped it. It just can't be a co-incident that somebody at new_user's company created the same event monitor with same name explicitly.


dollar

Thanks dollar ..

Just 'discovered' from the manuals that the event monitor is created by default when you create the database ..

And my desktop PE does have one too ..

Cheers

Sathyaram