Ahh, do it's actually that privilege, and not the "Magic of SYS" that causes this behaviour ?
Any user with ADMINISTER DATABASE TRIGGER privilege can log on even if the logon trigger raises an error.
Look into udump and you'll see Oracle complaining about the trigger's exception there.
------------------------------ *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto: oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Michael Haddon *Sent:* Thursday, September 14, 2006 09:25 *To:* JApplewhite@xxxxxxxxxxxxx
*Cc:* oracle-l@xxxxxxxxxxxxx *Subject:* Re: Restrict login for a particular user to be only from particul ar m achines
The trigger is working but when you raise the application error the insert gets rolled back.
The only way we were able to accomplish the logging of a failed login was to use the
declare pragma autonomous_transaction; begin
This way the insert gets committed when you raise the application error exception
Hope this helps