Before checking stats, execution plans and the like take a look at your query. I
presume that it is generated, otherwise you would probably say that a date belongs to
a month by using a BETWEEN the first and the thirty first rather than listing all the
31 days, would you ? Now perhaps the
In addition, since you're using the cost-based optimizer (CBO), make sure
that you've used dbms_stats to gather statistics on all the objects
involved in the query recently. If you have any columns where histograms
would be useful, make sure you've gathered histograms for those columns.
Well, I'd start by writing the date part as :
MEPAI.MPAI_AS_OF_DATE between to_date('03/01/2003','MM/DD/') and
to_date('03/31/2003','MM/DD/')
It will at the very least make the query easier to read and understand
(also for the optimizer : it will know it's filtering on a range instead
Hi New DBA,
Further to what Stephane has said below, the following two stats in your
initial post are interesting ...
consistent gets 559985
table fetch continued row 212027
That suggests that there is a fair amount of row
In addition to the excellent advice you have already received,
let me congratulate you on taking the time to format your
code and trace data so that it is readable.
There are folks that are known to skip long posts such as
this when poorly formatted and difficult to read. ;)
Jared
New
02:20
To: Multiple recipients of list ORACLE-L
Subject: Re: Tuning help required
Well, I'd start by writing the date part as :
MEPAI.MPAI_AS_OF_DATE between
to_date('03/01/2003','MM/DD/') and
to_date('03/31/2003','MM/DD/')
It will at the very least make the query easier
