Re: What to do if a logon trigger get invalidated ?

Also note. If your user has the system privilege ADMINISTER DATABASE TRIGGER granted
to it , the trigger will not fire . The DBA role has it. (8.1.7 and probably 9i)

Stephen C. Ashmore
Brainbench MVP for Oracle Administration http://www.brainbench.com
Author of: 'So You Want to be an Oracle DBA?'

"Anton Buijs" <aammbuijs_at_xs4all.nl> wrote in message news:3dc17a59$0$46617$e4fe514c_at_news.xs4all.nl...
> Next works in V8.1.7 (Unix), can't say it for V9.2.
> 1. On the server itself do connect internal (in 9.2: sqlplus / as sysdba).
> Disable the trigger.
> 2. Set the (Oracle internal so undocumented) init.ora parameter
> _system_trig_enabled = FALSE, stop/start the database and then disable the
> trigger. Restart again with the parameter removed.
>
> Hans Erik Busk <tbf_at_cn.stam.dk> schreef in berichtnieuws
> hg32su8adhreu8tq0o8hmmmvct03vorj4l_at_4ax.com...
> | I have experimented a bit with on logon triggers, and it seems such a
> | trigger can create a single point of failure that can bring down the
> | whole database for good.
> | If the trigger becomes invalidated (a table it relies on becomes
> | corrupted for instance), it is not possible for anyone to log on, not
> | even sys as sysdba !
> | In effect this prevents any rescue operations.
> | Or have I overlooked something ?
> | Oracle 9.2 on W2K
> |
> | p.s. Not an acute problem, it was a test database
> |
> | Hans Erik Busk
>
Received on Fri Nov 01 2002 - 05:47:30 CST