SET the optimizer_mode parameter to CHOOSE, then re compute the
statistics. and run it again. the optimizer will make a decision, either
to use the Index or Full table scan.
which ever is faster
cheers

> You could try hints especially the index hint.
>
> http://www.psoug.org/reference/hints.html
>
> Jerry Whittle
> COINS DBA
> NCI Information Systems Inc.
> jerome.whittle.[Email address protected]
> 618-622-4145
> -----Original Message-----
> From: Tavousi Mahnaz
> [mailto:oracledba-ezmlmshield-x45528690.[Email address protected]
>
> Hello,
>
> I have a table which is partitioned.
> When I run a query with different scenario and take a look at the
> execution plan , oracle either uses index or full scan.
> When it uses index the response time is 1 sec but when it uses table
> scan the response time is 3 sec.
> I have to mention that all the column I am using in my select are part
> of index. I am wondering if there is any way to force the optimizer to
> apply index only.
>
> Thanks
>
> Mahnaz Tavousi
>> ACNielsen Company of Canada
>> Tel: 905-475-3344 ext 2615
>> e-mail: Mahnaz.[Email address protected]
>
>
> --------
> website: http://www.LazyDBA.com
> Please don't reply to RTFM questions
> Oracle documentation is here: http://tahiti.oracle.com
> To unsubscribe: see http://www.lazydba.com/unsubscribe.html
> To subscribe: see http://www.lazydba.com
> By using this list you agree to these
> terms:http://www.lazydba.com/legal.html
>
>


///\\
(@ @)
+--oOO--(_)--Ooo--+
|Yoseph I Fahed|
+-----------------+
|__|__|
|| ||
ooO Ooo



Oracle LazyDBA home page