RE: Re: Row level security and latch waits

Hi Raj,
Vadim is right and if RLS is implemented without application context then there would be hard parses especially if there are literals in the policy function . We have a client warehouse with about 500 users and 300 tables and FGAC has been working very well and we do not see latch waits.

The policy function has to be devoid of literals as vadim indicated. We ste up the policy function based on the application context and in order to look at the where clause generated, an evetn can be set.

Hope this helps.

Thanks
Madhavan
http://www.dpapps.com

On Tue, 19 Aug 2003 12:24:26 -0800, "Gorbounov,Vadim" <vadim.gorbounov_at_liberate.com> said:
> Jack,
> You are right, app context is treated as a bind variable, but someone may
> decide not to use it in RLS policy function. Example (maybe a little
> unreal
> but valid):
>
> CREATE OR REPLACE PACKAGE BODY Oe_security AS
>
> FUNCTION Custnum_sec (D1 VARCHAR2, D2 VARCHAR2) RETURN VARCHAR2
> IS
> D_predicate VARCHAR2 (2000)
> BEGIN
> D_predicate = 'create_date > '''||to_char(sysdate-1)||'''';
> RETURN D_predicate;
> END Custnum_sec;
> END Oe_security;
>
> Hence hard parses.
>
> Vadim

-- 
Madhavan Amruthur
DecisionPoint Applications

-- 
http://www.fastmail.fm - mmm... Fastmail...
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Madhavan Amruthur
  INET: mad5698_at_fastmail.fm

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: ListGuru_at_fatcity.com (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).