According to the Oracle 8i docs, any errors caused by logon triggers will
cancel the login attempt, unless you are logging in as SYSTEM. Don't know
about startup triggers though, I assume there are similar fallbacks in place
so the database can at least come up in restricted session mode.
Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk> wrote in message
news:939288159.24594.0.nnrp-11.9e984b29_at_news.demon.co.uk...
>
> That's what I'd call a stroke of genius.
>
> I feel very twitchy about logon/startup etc. triggers
> for exactly the experience you found - what if they
> go wrong and no-one can connect every again. So
> I'll second your idea of having a scratch database
> that can be thrown away at the drop of a hat. In fact
> I have advised people to buy a small Sun or HP
> to run as a standalone one-horse database server
> for exactly such tests.
>
> --
>
> Jonathan Lewis
> Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk
>
> > So finally when I have already
> given up
> >all the hopes and was preparing to recreate the database (it is only a
> >testing instance, thank god), I tried with the last shot in the dark:
> >
> >DECLARE
> > PRAGMA autonomous_transaction;
> >BEGIN
> > EXECUTE IMMEDIATE 'DROP TRIGGER trigger_name';
> >END;
> >
> >And guess what - it succeeded, the trigger was dropped and I was able
> >to log on normally again.
> >
>
>
>
Received on Thu Oct 07 1999 - 14:29:50 CDT
