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

From: Pete Sharman <peter.sharman_at_oracle.com>
Date: 31 Oct 2002 10:08:53 -0800
Message-ID: <aprrjl02eio@drn.newsguy.com>

In article <hg32su8adhreu8tq0o8hmmmvct03vorj4l_at_4ax.com>, Hans says...
>
>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

You should ALWAYS be able to log on as SYSDBA to fix this. Can you post the results of trying to connect as SYSDBA with an invalid logon trigger?

HTH. Additions and corrections welcome.

Pete

SELECT standard_disclaimer, witty_remark FROM company_requirements; Received on Thu Oct 31 2002 - 12:08:53 CST