Hello, I am not sure that this is the best way to group OEM events, but it works for
us. I have created the following events in the event library, and I use these for
each database I register.
Node Status: triggered every 2 mins : checks up/down status : critical
Database Status: triggered every 2 mins : checks up/down status : critical
Listener Status: triggered every 2 mins : checks up/down status : critical
5 Minute Database Checks: checks for alerts, archive_dest % full, archiver hung :
critical
5 Minute Node Checks: checks for disks full, cpu utilization : critical
15 Minute Database Checks: checks for tablespace full, DB limits, corruption, and
utilization : warning/critical
15 Minute Node Checks: checks for cpu paging and swap full : warning/critical
Daily Database Checks: triggered every 12 hours : checks various space allocation and
utilization : warning
Database Performance Checks: triggered every 24 hours : routine database performance
checks : warning
Traci L. Rebman
Database Administrator
D & E Communications, Inc.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Traci Rebman
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
