execution plans
From: geos <geos_at_nowhere.invalid>
Date: Tue, 18 Oct 2011 22:02:01 +0200
Message-ID: <j7km0a$iks$1_at_news.task.gda.pl>
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:
Date: Tue, 18 Oct 2011 22:02:01 +0200
Message-ID: <j7km0a$iks$1_at_news.task.gda.pl>
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.miscReceived on Tue Oct 18 2011 - 15:02:01 CDT