Re: Keeping my triggers enabled

If you are on 8i, you can have a DDL trigger that will fire off on the 'alter trigger disable' command and will throw an exception. However, due a limitation in 8.1.x, it will only work if the actual schema owner of the trigger will attemopt to disable it. But then again there should't be too many dba account on your database, right?

In article <8tppa2$jdr$1_at_faraday.a2000.nl>,   "jantah" <jantah_at_hot.mail.com> wrote:
> Hi all,
>
> Because we wanted to be absolutely sure nobody would accidently
 disable a
> trigger on our database, I wrote a little shell script to keep an eye
 on
> them. It's basically a loop that checks the dba_triggers view using
> SQL*Plus every three seconds. If it finds any disabled triggers, the
> script will perform an immediate shutdown of the database. I agree
 that
> this is a bit drastic (I aptly named the script after my sisters
 pitbull
> terrier ;-), but we considered this the most secure option.
>
> Question is, if this the best way to do this? Starting SQL*Plus every
> three seconds for a check this simple looks a bit steep to me. Is
 there
> another way to perform this check from a shell script? Is there a way
 to
> make an SQL script sleep for three seconds?
>
> --
> Jan
>
> jantah_at_hot.mail.com
> ... and you know what to do with hot.mail, right ?
>

--
                 Alex Shterenberg


Sent via Deja.com http://www.deja.com/
Before you buy.