| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Restrict login for a particular user to be only from particul ar machines
Yep, that's it, as I determined independently, but not in time to avoid being scooped by Tanel. No shame in that, though!
Paul Baumgartel
CREDIT SUISSE
Information Technology
DBA & Admin - NY, KIGA 1
11 Madison Avenue
New York, NY 10010
USA
Phone 212.538.1143
paul.baumgartel_at_credit-suisse.com
www.credit-suisse.com
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Tanel Poder
Sent: Thursday, September 14, 2006 10:12 AM
To: m.haddon_at_comcast.net; JApplewhite_at_austinisd.org
Cc: oracle-l_at_freelists.org
Subject: RE: Restrict login for a particular user to be only from particul ar m achines
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.
Tanel.
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Michael Haddon
Sent: Thursday, September 14, 2006 09:25
To: JApplewhite_at_austinisd.org
Cc: oracle-l_at_freelists.org
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
Mike
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Sep 14 2006 - 09:18:19 CDT
 |
 |