Ha, good one. Yep, makes sense to get it working first. Sorry if I went
down the wrong path on this thread. Probably did.
By the way, did you try out event 10730, which will show information
about FGAC stuff on the first parse (not, repeat, not after that)? Never
tried it myself, but it should show the extra stuff that is later
hidden. Haven 't bothered to test it myself, of course.
Mogens
Raj Jamadagni wrote:
> Mogens,
>
> Very true, but our situation was w/o index the sql wouldn 't run. The form would freeze and the
> developer insisted that nothing else (except the VPD) will work. So, my colleague who was
> attending OOW 2003, checked with Oracle guys who asked "is there a index on *those* columns? ". We
> didn 't have one, created and that process finally started working.
>
> Give the options ...
>
> 1 > not working
> and
> 2 > does more LIO
>
> I didn 't want to think about option 2. ... getting that stupid thing to work was a priority. So,
> as we summarized in our case ... the problem wasn 't the index but the VPD. And don 't you love when
> they come up with "1=1 " conditions where there is nothing to filter by?
>
> Cheers
> Raj
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
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
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
