Re: How do you know when something is wrong with your DB?

On Wed, 12 Feb 1997 17:01:17 -0800, Simon Goland <sg_at_mda.ca> wrote:

Hi!

I think, that mailing grep-results from the alert-file won't help you in a productive-environment. A better way to get thos information quickly are SNMP-agents. Have a look for this and also for the enterprise-manager (v 1.22). We are experimenting with these things to resolve the same problems, that you have.

>When something abnormal happens, but not really crucial, how do you know
>it happened? Say, a datafile suddenly becomes corrupted, or you lose a
>redo log file, or some other act of supreme (and unfriendly) powers that
>does not cause Oracle to shutdown.
>
>One way is, of course, all the phone calls from users who cannot use the
>DB anymore. But I am looking for something more proactive. For example,
>a cron job (on Unix) that will periodically scan the alert log file,
>look for errors and email them to me.
>
>Any other ideas/suggestions?
>
>Thanks,
>--
>[ Simon Goland B-)> sg_at_mda.ca ]
>[ Without action there is no change ]
Received on Fri Feb 14 1997 - 00:00:00 CST