Re: Explain plan dilemma

Net,

   Thank you for your assistance, but the answer to my question is as follows.

select ...
from plan_table
connect by prior id = parent_id
  and statement_id = 'a'
start with id = 1
  and statement_id = 'a'

   Notice that the where clause is gone, and the start clause has an extra condition.

Mark

Mark Johnson (markjo_at_netcom.com) wrote:
: Hello,
:
: select lpad(' ',2*level)||operation||' '||options||' '||object_name
: from plan_table
: where statement_id = '1'
: connect by prior id = parent_id
: and statement_id = '1'
: start with id = 1
 

: What is the problem here. This works fine if there are only
: statements with statements_ids of '1' in the plan_table. Otherwise it
: returns too many. The output looks something like the following.
 

: INDEX UNIQUE SCAN TABLES_UK1
: [add 16 of the above line here]
: INDEX UNIQUE SCAN TABLES_UK1
: TABLE ACCESS BY ROWID TABLES (1)
: INDEX UNIQUE SCAN TABLES_UK1
: INDEX UNIQUE SCAN TABLES_UK1
 
: Thanks
Received on Wed Jul 19 1995 - 00:00:00 CEST