Re: VPD or parameterized view.... same parses count
Date: Thu, 11 Jun 2009 11:31:32 -0400
Message-ID: <49d668000906110831w5a57e6a4k542625f6f7b40f69_at_mail.gmail.com>
- that may not be hard parses
what "Misses in library cache during parse:" says?
2. how did you create VPD policy (for your VPD tests), especially static_policy and policy_type parameters?
On Thu, Jun 11, 2009 at 11:18 AM, Ujang
Jaenudin<ujang.jaenudin_at_gmail.com> wrote:
> dear all,
>
> I have heard that using VPD, there is an issue with hard parsing.
> I'm tried using parameterized view...with sys_contex, but same parses
> result either vpd or view..
>
> create or replace view vw_userdata as
> select * from user_data
> where user_id=decode(sys_context('''USERENV''','''SESSION_USER'''),'USER1',1,2);
>
> when call 4 times either view or VPD, this tkprof always give me 4 parses :
>
> call count cpu elapsed disk query current rows
> ------- ------ -------- ---------- ---------- ---------- ---------- ----------
> Parse 4 0.00 0.00 0 0 0 0
> Execute 4 0.00 0.00 0 1 0 0
> Fetch 7 0.00 0.00 0 31 0 3
> ------- ------ -------- ---------- ---------- ---------- ---------- ----------
> total 15 0.00 0.00 0 32 0 3
>
>
> so, any other method to avoid hard parsing for security purpose?
>
> --
> thanks and regards
> ujang | oracle dba | mysql dba
> jakarta - indonesia
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
-- Alex Fatkulin, http://afatkulin.blogspot.com http://www.linkedin.com/in/alexfatkulin -- http://www.freelists.org/webpage/oracle-lReceived on Thu Jun 11 2009 - 10:31:32 CDT