Application Context is used to implement FGAC (aka RLS).  You need to read
those sections in the Concepts doc.

Jack C. Applewhite
Database Administrator
Austin Independent School District
Austin, Texas
512.414.9715 (wk)
512.935.5929 (pager)
[EMAIL PROTECTED]



                                                                                       
                                       
                      <[EMAIL PROTECTED]                                               
                                        
                      >                        To:       Multiple recipients of list 
ORACLE-L <[EMAIL PROTECTED]>          
                      Sent by:                 cc:                                     
                                       
                      [EMAIL PROTECTED]        Subject:  Re: Re: Row level security 
and latch waits                           
                      .com                                                             
                                       
                                                                                       
                                       
                                                                                       
                                       
                      08/19/2003 02:19                                                 
                                       
                      PM                                                               
                                       
                      Please respond to                                                
                                       
                      ORACLE-L                                                         
                                       
                                                                                       
                                       
                                                                                       
                                       




i wasny referring to application contexts. I was referring to just using a
policy based on dbms_rls.

thats different isnt it?
>
> From: [EMAIL PROTECTED]
> Date: 2003/08/19 Tue PM 03:14:28 EDT
> To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
> Subject: Re: Re: Row level security and latch waits
>
>
> OK, I went and looked in the 8i Concepts manual.  It seems pretty clear
> that Application Context variables are used as bind variables.  It may
have
> changed for 9i, but I can't see how or why.
>
> "Application Context
>
>
> Application context facilitates the implementation of fine-grained access
> control. It allows you to implement security policies with functions and
> then associate those security policies with applications. Each
application
> can have its own application-specific context. Users are not allowed to
> arbitrarily change their context (for example, through SQL*Plus).
>
>
> Application contexts permit flexible, parameter-based access control,
based
> on attributes of interest to an application. For example, context
> attributes for a human resources application could include "position",
> "organizational unit", and "country" while attributes for an order-entry
> control might be "customer number" and "sales region".
>
> You can:
> - Base predicates on context values
> - Use context values within predicates, as bind variables    <<<< NOTE
THIS
> LINE.>>>>>
> - Set user attributes
> - Access user attributes "
>
> Jack C. Applewhite
> Database Administrator
> Austin Independent School District
> Austin, Texas
> 512.414.9715 (wk)
> 512.935.5929 (pager)
> [EMAIL PROTECTED]
>
>
>
>

>                       <[EMAIL PROTECTED]

>                       >                        To:       Multiple
recipients of list ORACLE-L <[EMAIL PROTECTED]>
>                       Sent by:                 cc:

>                       [EMAIL PROTECTED]        Subject:  Re: Re: Row
level security and latch waits
>                       .com

>

>

>                       08/19/2003 01:39

>                       PM

>                       Please respond to

>                       ORACLE-L

>

>

>
>
>
>
> its just appending a where clause. its not binding it.
>
> im not familiar with contexts. never worked with them. someone correct me
> if im wrong here? Could have sworn i read that somewhere.
>
> i looked up application contexts. they appear to be handled differently.
>
> am i wrong?
> >
> > From: [EMAIL PROTECTED]
> > Date: 2003/08/19 Tue PM 02:14:25 EDT
> > To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
> > Subject: Re: Row level security and latch waits
> >
> >
> > RLS doesn't use bind variables?  How then does Oracle treat the
> Application
> > Context variables that you include in the predicates generated by the
> > Security Policy functions?  If those aren't bind variables then I guess
I
> > don't know what bind variables are.
> >
> > Please refer me to the documentation on which your assertion is based.
> >
> > Thanks.
> >
> > Jack C. Applewhite
> > Database Administrator
> > Austin Independent School District
> > Austin, Texas
> > 512.414.9715 (wk)
> > 512.935.5929 (pager)
> > [EMAIL PROTECTED]
> >
> >
> >
> >
>
> >                       <[EMAIL PROTECTED]
>
> >                       >                        To:       Multiple
> recipients of list ORACLE-L <[EMAIL PROTECTED]>
> >                       Sent by:                 cc:
>
> >                       [EMAIL PROTECTED]        Subject:  Re: Row level
> security and latch waits
> >                       .com
>
> >
>
> >
>
> >                       08/19/2003 10:44
>
> >                       AM
>
> >                       Please respond to
>
> >                       ORACLE-L
>
> >
> >
> >
> > row level security doesnt use bind variables.
> >
> > dont know if there is a way to get it to use them. thats probably your
> > problem.
> > >
> > > From: "Jamadagni, Rajendra" <[EMAIL PROTECTED]>
> > > Date: 2003/08/19 Tue AM 11:19:24 EDT
> > > To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
> > > Subject: Row level security and latch waits
> > >
> > > hi all,
> > >
> > > in the latest code release, a group implemented RLS and since then
> > spotlight
> > > is constantly flagging 'latch waits' in the system. Yesterday the
latch
> > > waits were upwards of 90%.
> > >
> > > Most active sessions seem to run the policy function defined as part
of
> > RLS.
> > > The worst part was all this wait was only on one node, the other node
> was
> > > healthy.
> > >
> > > While we are trying to capture more information, anything else that
we
> > can
> > > do? Any ideas?  TIA
> > >
> > > Raj
> > >
> >
>
----------------------------------------------------------------------------

>
> >
> > > ----
> > > Rajendra dot Jamadagni at nospamespn dot com
> >
> >
> > >
> > hi all,
> >
> >
> > in the latest code release, a group implemented RLS and since then
> > spotlight is constantly flagging 'latch waits' in the system. Yesterday
> the
> > latch waits were upwards of 90%.
> >
> >
> > Most active sessions seem to run the policy function defined as part of
> > RLS. The worst part was all this wait was only on one node, the other
> node
> > was healthy.
> >
> >
> > While we are trying to capture more information, anything else that we
> can
> > do? Any ideas?  TIA
> >
> >
> > Raj
> >
>
--------------------------------------------------------------------------------

> >
> > Rajendra dot Jamadagni at nospamespn dot com
> >
> >



-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: 
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to