Re: OEM alert suggestions

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 . . .

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

On Wed, 4 Dec 2002 14:51:52 -0000, "Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote:

>My suggestions off the top of my head
>tablespace full 70% and 85%
>node up/down
>db up/down
>fast segment growth say 5 and 10 per week.
>
>I'd play with one or two of these and with the alert schedules to see how
>well this works.
>
>It is self evidently not a complete list.
>--
>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
>
>******************************************
>"Ed Stevens" <spamdump_at_nospam.noway.nohow> wrote in message
>news:3dee03d3.49593932_at_ausnews.austin.ibm.com...
>> Platform: Oracle 8.1.7, NT, Win2k, and *nix
>>
>> I have just started playing with OEM and after a few small scale trials of
>the
>> mechanics, have e-mail alert notification working. Now I'd like to set up
>> full-blown demo against a couple of databases and am looking for some
>advice on
>> a useful set of alerts and their "triggering" parm values
>>
>> TIA
>> --
>> Ed Stevens
>> (Opinions expressed do not necessarily represent those of my employer.)
>
>

--
Ed Stevens
(Opinions expressed do not necessarily represent those of my employer.)