Re: restrict connections to some instances in RAC

From: Tanel Põder <tanel.poder.003_at_mail.ee>
Date: Tue, 17 Feb 2004 11:08:14 +0200 (EET)
Message-ID: <03ae01c3f5aa$e3c638d0$0c00640a@poder>

Hi, are you sure you are actually killing the session, because you can't kill your own session with alter system kill session. But anyway, any unhandled exception in logon trigger will prevent users without 'administer database trigger' from logging in.

One more thing you could do to direct clients to correct instances, is using different service names for different client types and assigning the service names to relevant instances. But the logon trigger should remain there, just in case (if you aren't doing excessive logons all the time).

Tanel.

Original Message ----- From: "Khedr, Waleed" <Waleed.Khedr_at_FMR.COM> To: <oracle-l_at_freelists.org> Sent: Friday, February 13, 2004 7:01 AM Subject: restrict connections to some instances in RAC

> Is there a clean way to restrict connections for certain users to specific
> instances in RAC environments?
>
> What I have now is a logon trigger that kills the session.
>
> Thanks
>
> Waleed
> ----------------------------------------------------------------
> Please see the official ORACLE-L FAQ: http://www.orafaq.com
> ----------------------------------------------------------------
> To unsubscribe send email to: oracle-l-request_at_freelists.org
> put 'unsubscribe' in the subject line.
> --
> Archives are at http://www.freelists.org/archives/oracle-l/
> FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
> -----------------------------------------------------------------

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Tue Feb 17 2004 - 03:08:14 CST