Re: FGAC

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Mon, 25 Nov 2002 12:32:55 -0000
Message-ID: <art5j0$i9r$1$8300dec7@news.demon.co.uk>

There are indications from Oracle (but I can't find the reference in the manual any more) that you should restrict the generated predicates to calls to sys_context(), rather than adding tables.

However, this can still change access paths - especially in 8.1, and especially if you have outer joins on the controlled tables - for example where a path had an index-only
option pre-control, but has to visit the table to check a column due to the security predicate.

--
Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

Next Seminar dates:
(see http://www.jlcomp.demon.co.uk/seminar.html )

____Denver_______December 2/4
____England______January 21/23


The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html





Niall Litchfield wrote in message
<3de217f9$0$8507$ed9e5944_at_reading.news.pipex.net>...


>"Noodles" <noodles_at_aol.com> wrote in message

>news:20021125064915.27419.00000083_at_mb-ct.aol.com...

>> Make your SQL is tuned perfectly because as you know, FGAC just

appends


>the SQL

>> from the "rule".

>

>Its always seemed to me that by doing this (adding silently to the

where


>clause) FGAC *if added retrospectively to an application* could screw

up


>access paths. Have you found this in practice or not?

>

>

>--

>Niall Litchfield

>Oracle DBA

>Audit Commission UK

>*****************************************

>Please include version and platform

>and SQL where applicable

>It makes life easier and increases the

>likelihood of a good answer

>

>******************************************

>

>

Received on Mon Nov 25 2002 - 06:32:55 CST