There isn't...Jack was joking and I was playing along. 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@xxxxxxxxxxxxxxxxx www.credit-suisse.com -----Original Message----- From: rjamya [mailto:rjamya@xxxxxxxxx] Sent: Wednesday, September 13, 2006 4:01 PM To: paul.baumgartel@xxxxxxxxxxxxxxxxx Cc: JApplewhite@xxxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx Subject: Re: Restrict login for a particular user to be only from particul ar m achines I don't think there is a before logon trigger ... Raj On 9/13/06, Baumgartel, Paul < paul.baumgartel@xxxxxxxxxxxxxxxxx <mailto:paul.baumgartel@xxxxxxxxxxxxxxxxx> > wrote: Jack, Yes, that would do the trick nicely, wouldn't it? 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@xxxxxxxxxxxxxxxxx <mailto:paul.baumgartel@xxxxxxxxxxxxxxxxx> www.credit-suisse.com <http://www.credit-suisse.com> -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx> [mailto: <mailto:oracle-l-bounce@xxxxxxxxxxxxx> oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of JApplewhite@xxxxxxxxxxxxx <mailto:JApplewhite@xxxxxxxxxxxxx> Sent: Wednesday, September 13, 2006 2:39 PM To: oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx> Subject: RE: Restrict login for a particular user to be only from particul ar m achines Paul, To prevent logon, shouldn't this be a Before Logon trigger? Jack C. Applewhite - Database Administrator Austin (Texas) Independent School District 512.414.9715 (wk) / 512.935.5929 (pager) I feel so unnecessary. -- Rufus Thomas ( "Do the Funky Chicken") "Baumgartel, Paul" < paul.baumgartel@xxxxxxxxxxxxxxxxx <mailto:paul.baumgartel@xxxxxxxxxxxxxxxxx> > Sent by: oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx> 09/13/2006 01:24 PM Please respond to paul.baumgartel@xxxxxxxxxxxxxxxxx <mailto:paul.baumgartel@xxxxxxxxxxxxxxxxx> To "'Bobak, Mark'" < Mark.Bobak@xxxxxxxxxxxxxxx <mailto:Mark.Bobak@xxxxxxxxxxxxxxx> >, salem.ghassan@xxxxxxxxx <mailto:salem.ghassan@xxxxxxxxx> cc oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx> Subject RE: Restrict login for a particular user to be only from particul ar m achines Thanks for all the replies. My initial attempts used an AFTER LOGON ON SCHEMA, not DATABASE, trigger. However, I'm now stymied in a simple test case: the following SYS trigger is firing, but no error appears on login. create or replace trigger verify_client after logon on database when (user='PB') begin insert into pb.foo values('Test'); commit; raise_application_error(-20999,'Not authorized'); end; / Here's what happens: SQL> @conn pb/pb Connected. PB@xxxxxxxxxxxxxxxx <mailto:PB@xxxxxxxxxxxxxxxx> > select * from foo; BAR -------------------- Test PB@xxxxxxxxxxxxxxxx <mailto:PB@xxxxxxxxxxxxxxxx> > @conn pb/pb Connected. PB@xxxxxxxxxxxxxxxx <mailto:PB@xxxxxxxxxxxxxxxx> > select * from foo; BAR -------------------- Test Test As you can probably guess, I added the "insert into pb.foo" to the trigger to verify that it is firing. What's wrong here? Thanks 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@xxxxxxxxxxxxxxxxx <mailto:paul.baumgartel@xxxxxxxxxxxxxxxxx> www.credit-suisse.com <http://www.credit-suisse.com> ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: <http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== -- ---------------------------------------------- Got RAC? ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ==============================================================================