raise an error (raise_application_error, or simply raise any_error)
Right, but if the machine name isn't one of the allowed machines, what action does the trigger take?
*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:* Ghassan Salem [mailto:salem.ghassan@xxxxxxxxx] *Sent:* Wednesday, September 13, 2006 12:29 PM *To:* paul.baumgartel@xxxxxxxxxxxxxxxxx *Cc:* oracle-l@xxxxxxxxxxxxx *Subject:* Re: Restrict login for a particular user to be only from particular m achines
use a logon trigger to test for the machine's name/ip rgds
On 9/13/06, Baumgartel, Paul <paul.baumgartel@xxxxxxxxxxxxxxxxx > wrote: > > All, > > A client wants to be able to limit login for particular database user to > be from a specified set of client machines. My understanding of login > restriction at the listener level is that it is possible only to limit all > database logins based on machine. I've been experimenting with login > triggers that inspect sys_context('userenv','host'), but haven't figured out > how to prevent the session from proceeding if the client machine name is not > in the approved list. If anyone has any ideas or suggestions I'd be most > grateful. > > 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 > 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 > ============================================================================== > > ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: