Re: session time model issue

From: Tanel Poder <tanel_at_tanelpoder.com>
Date: Wed, 9 Jan 2013 23:51:36 +0700
Message-ID: <CAMHX9JJrMAuZcdktd3HCRSZJMgGVMPU+2KD25s=4U9aTWkneHg_at_mail.gmail.com>

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.

> >>

> >> As this is for one session I assume there is no possibility the sum of

> >> ingredients is more than DB time (of course by much), so it seems

> >> reasonable to assume sql execute elapsed time is execute, fetch and

> >> parse, which is against the docs.

>



--
http://www.freelists.org/webpage/oracle-l

Received on Wed Jan 09 2013 - 17:51:36 CET