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

On 3 Nov 2002 14:01:24 -0800, Pete Sharman <peter.sharman_at_oracle.com> wrote:

>What you have here is a combination of errors that have nothing to do with an
>invalid logon trigger. The connect / as sysdba command fails because
>REMOTE_LOGIN_PASSWORDFILE is SHARED. That means (and I quote from the doc)
>"More than one database can use a password file. However, the only user
>recognized by the password file is SYS." IN other words, you can only connect
>as SYS using SYSDBA. Reset the parameter to EXCLUSIVE and the connection should
>work.

Thank you for your response, I have however a few clarifying comments:

I have also tried "REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE" with the same result (i.e. insufficient priv, when logging in as / as sydba).

The interesting question is if there is any difference in privileges between the two:
"connect / as sysdba" or
"connect sys/password as sysdba"

Oh the good old times with svrmgrl and connect internal ! ;-)

>The connect sys/password as sysdba is running into a different problem. THe
>database's knickers seem to be in a complete twist, resulting in a lost
>connection (ORA-03113) so the next startup command also fails because you're no
>longer connected to Oracle.

What i didn't point out was the odd message i get when  

"connect sys/pw as sydba"
 "Connected to an idle instance"

because the instance is certainly not idle, another user logged on before the trigger became invalid is still connected and able among other things to disable the trigger.

>necessary underscore parameter. This is not something I would recommend (using
>underscore parameters to get around problems there are more supported ways of
>fixing, I mean).

I agree completely, but at least this could be a way of salvage in the rather unlikely event of the trigger becoming invalid.

Hans Erik Busk Received on Mon Nov 04 2002 - 03:03:18 CST