| 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 connections to some instances in RAC
Works perfectly, thanks.
This is what I tried first which did not work because I was testing the
connections using accounts that have DBA privilege and this why I had =
to
spawn jobs to kill the sessions :)
This is cleaner.
Regards,
Waleed
-----Original Message-----
From: Tanel P=F5der [mailto:tanel.poder.003_at_mail.ee]
Sent: Wednesday, February 18, 2004 6:30 AM
To: oracle-l_at_freelists.org
Subject: Re: restrict connections to some instances in RAC
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.
> Thanks. I use dbms_job to spawn a proc to kill the session.=3D20
>
> The connection continues normally when I raise unhandled exception in =
=3D
> the
> logon trigger.
> A trace file gets generated that shows that some problems took place =
=3D
> and
> that the database connection is continuing with its connection.
> Actually I found that the a lot of things get ignored or behave =3D
> 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=3DF5der [mailto:tanel.poder.003_at_mail.ee]
> Sent: Friday, February 13, 2004 5:10 PM
> To: oracle-l_at_freelists.org
> Subject: Re: restrict connections to some instances in RAC
>
>
> Hi, are you sure you are actually killing the session, because you =
=3D
> can't
> kill your own session with alter system kill session. But anyway, any
> unhandled exception in logon trigger will prevent users without =3D
> 'administer
> database trigger' from logging in.
>
> One more thing you could do to direct clients to correct instances, =
is =3D
> using
> different service names for different client types and assigning the =
=3D
> service
> names to relevant instances. But the logon trigger should remain =
there, =3D
> 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 =
=3D
> 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
> -----------------------------------------------------------------
> ----------------------------------------------------------------
> 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
> -----------------------------------------------------------------
>
-- 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 Wed Feb 18 2004 - 14:55:28 CST
 |
 |