Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.tools -> Re: Explain Plan

Re: Explain Plan

From: Sybrand Bakker <gooiditweg_at_nospam.demon.nl>
Date: Fri, 04 Feb 2005 15:36:22 +0100
Message-ID: <ru1701t08i0o5khpa4nvc7mj2udn3p2pe7@4ax.com>


On 4 Feb 2005 06:06:58 -0800, amerar_at_iwc.net wrote:

>
>Well, this was the output of running some PL/SQL procedure. There is
>nothing wrong with this query. What I am getting at, is how would one
>interpert all that?
>
>I mean, I'd like to be able to figure out something like: First it did
>a full table scan using an index, then it did a sort on those records,
>next it joined with table B using columns C & D, then it did a full
>table scan without an index on table B.........
>
>Knowing exactly what happened and in what order helps to understand the
>path that the query took. I have no clue by looking at this what
>happened first, and to what objects and what was done.........that is
>what I am trying to accomplish.
>
>Arthur

That is why Oracle published documentation, in your case the Performanace Tuning manual.
It looks strange you are trying to improve on recursive sql. Apparently you are also still using Dictionary Managed Tablespaces (see the reference to fet$ in your explain, fet$ is the table storing free extents)

--
Sybrand Bakker, Senior Oracle DBA
Received on Fri Feb 04 2005 - 08:36:22 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US