Message-ID: <025201c3f612$9ce9d440$73f823d5@porgand>
From: =?iso-8859-1?Q?Tanel_P=F5der?= <tanel.poder.003@mail.ee>
To: <oracle-l@freelists.org>
References: <D91D9D5A73FC694BBC52F1EB26AD410FA2E4AF@MSGBOSCLD2WIN.DMN1.FMR.COM>
Subject: Re: restrict connections to some instances in RAC
Date: Wed, 18 Feb 2004 13:30:27 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: oracle-l-bounce@freelists.org
Errors-To: oracle-l-bounce@freelists.org
Precedence: normal
Reply-To: oracle-l@freelists.org

Waleed,

The logon trigger unhandled exception handling behaviour is dependent on
whether the user trying to log on does have the "administer database
trigger" privilege or not. If she doesn't, then user gets an error message
and nothing is written to trace files. If she does have the priv, then she
is let in anyway and an error is written to trace.

I have tested it in 10g, 9i and I believe it works the same way in 8i as
well.

Tanel.


----- Original Message ----- 
From: "Khedr, Waleed" <Waleed.Khedr@FMR.COM>
To: <oracle-l@freelists.org>
Sent: Tuesday, February 17, 2004 4:06 PM
Subject: RE: restrict connections to some instances in RAC


> Thanks. I use dbms_job to spawn a proc to kill the session.=20
>
> The connection continues normally when I raise unhandled exception in =
> the
> logon trigger.
> A trace file gets generated that shows that some problems took place =
> and
> that the database connection is continuing with its connection.
> Actually I found that the a lot of things get ignored or behave =
> differently
> in logon triggers, and it seems to me that it's designed this way.
>
> Did you test this "unhandled exception" in logon triggers? What Oracle
> release?
>
> Thanks
>
> Waleed
>
> -----Original Message-----
> From: Tanel P=F5der [mailto:tanel.poder.003@mail.ee]
> Sent: Friday, February 13, 2004 5:10 PM
> To: oracle-l@freelists.org
> Subject: Re: restrict connections to some instances in RAC
>
>
> 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@FMR.COM>
> To: <oracle-l@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@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@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@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@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
-----------------------------------------------------------------