Re: session time model issue

From: Tanel Poder <tanel_at_tanelpoder.com>
Date: Wed, 9 Jan 2013 23:53:37 +0700
Message-ID: <CAMHX9J+Z1u_PDzM71Wq61uMCs=_ga6xCrwHSw4eKczxc+undZA_at_mail.gmail.com>



And similarly, when you run a SQL statement which has some PL/SQL functions in it (called again and again for each row) then the "sql execution time" and "PL/SQL execution time" are similarly double-counted due the recursive calls ...
I remember some bug(s) related to this too, but don't remember the bug ids ...
-- 
Tanel Poder
New Online Training! - http://blog.tanelpoder.com/seminar
The Voicee App - http://voic.ee



On Wed, Jan 9, 2013 at 11:51 PM, Tanel Poder <tanel_at_tanelpoder.com> wrote:


> Hi Remigiusz,
>
> This seems to happen (at least in some versions) when a (hard) parse
> causes recursive SQL execution (for data dictionary access, FGAC predicate
> generation etc) ...
>
> --
> Tanel Poder
> New Online Training! - http://blog.tanelpoder.com/seminar
> The Voicee App - http://voic.ee
>
>
> On Wed, Jan 9, 2013 at 3:09 PM, Remigiusz Sokolowski <
> remigiusz.sokolowski_at_nordea.com> wrote:
>
>> On 09.01.2013 04:48, Jeremy Schneider wrote:
>> > On Tue, 8 Jan 2013 12:49:44 +0100
>> > Remigiusz Sokolowski <remigiusz.sokolowski_at_nordea.com> wrote:
>> >
>> >> I have just reviewed the session time model gathered for a single
>> >> query. My concern is that parse time elapsed is nearly 97% (and
>> >> actually the whole amount is attributed to hard parse) of the DB time
>> >> and sql execute elapsed time is 99% of the DB time.
>>
>
-- http://www.freelists.org/webpage/oracle-l
Received on Wed Jan 09 2013 - 17:53:37 CET

Original text of this message