Re: OEM alert suggestions

"Ed Stevens" <spamdump_at_nospam.noway.nohow> wrote in message news:3def577f.49420532_at_ausnews.austin.ibm.com...
> OK, that'll give me a good start. Now another question.
>
> When creating an 'event', youI have the option of placing multiple targets
> (nodes, dbs, etc) and multiple tests under the single 'event'. How would
you
> recommned grouping (or not) these items? The simplistic approach would be
to
> have an 'event' contain only a single test against a single target. But
when
> you have multiple nodes, each with multiple databases, and each target
> requireing multiple tests . . . setting up all the necessary events starts
to
> look like generating a Cartesian product . . .

I have setup single event tests from multiple targets. I have tried to group databases into LIVE/TEST/DEV groups though helpfully not by using the built in groups feature. So for eg I have an event test LiveDatabaseDown which contains the test database down against all our live targets.

>
> And if you have multiple targets and/or tests under a single event, will
the
> notification message be sufficiently informative?

I get for example on the tablespace full test Name : TableSpace Full
Target Name : *********.audit-commission.gov.uk

Target Type : Database

Node Name : *********.audit-commission.gov.uk

Status : WARNING

Tablespace Full

Tablespace RBS is 75.24% full. 1.01376e+006 KBytes of free space remain.

WARNING Nov 27 2002 11:13:45 PM

So I get the db name, the node name and the actual warning. Which is enough for me. I should say that I have two colleagues who don't like the idea of being emailed warnings and so they run scripts/scrutinize logs etc. I have some sympathy with this approach.

--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer

******************************************