Re: execution plans

From: ddf <oratune_at_msn.com>
Date: Wed, 19 Oct 2011 13:32:55 -0700 (PDT)
Message-ID: <5df75879-53b1-498a-a6fa-d5acd79edb8e_at_a25g2000yqi.googlegroups.com>



On Oct 18, 1:02 pm, geos <g..._at_nowhere.invalid> wrote:
> there is a query which executes with two different plans when run on
> different accounts. this is generally understandable to me. but is there
> a way/algorithm to investigate the settings/configuration/permissions
> which have crucial influence on execution plans? for example:
>
> select * from emp where ename in ('KING','SMITH');
>
> execution plan as scott:
> 0 SELECT STATEMENT, koszt 24
> 1  COLLECTION ITERATOR PICKLER FETCH
>
> execution plan as sys:
> 0 SELECT STATEMENT, koszt 2
> 1  INLIST ITERATOR
> 2   TABLE ACCESS BY INDEX ROWID
> 3    INDEX RANGE SCAN
>
> is there anything in the above plans that suggests some parameter(s)
> which when set in sys session would give scott-like execution plan?
>
> thank you,
> geos
>
> --
> FUT: comp.databases.oracle.misc

A pickler fetch isn't what's executing against EMP, as Mladen pointed out. You might want to read here:

http://oratips-ddf.blogspot.com/2009/12/in-pickle.html

David Fitzjarrell Received on Wed Oct 19 2011 - 15:32:55 CDT

Original text of this message