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.

Justin Cave

At 02:49 AM 9/24/2003, you wrote:
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 generator could generate a BETWEEN if you are always interested by consecutive days?
Note that the GEO table is totally useless in the FROM clause. You return no data from it, and it is not needed to join together two tables you return data from. If you need it to check some data consistency, it should be in a subquery (IN or EXISTS, depending on the volumes of data to process), but best of all the problem should have been tackled at the root with referential integrity constraints. Even if you may have (always those b***y generators) it should be better located in a subquery - by the way, it might help you dispose of the UNIQUE (calling DISTINCT UNIQUE doesn't make it better :-)).


The condition of CUR_SYS_NO should be applied to the column from MEPAI, which you will encounter first, rather than the column from CUR, since they are equal.
Now you have to decide which of MEPAI or PRODUCTS should be the table you search first. It depends on the selectivity of your data. Be certain that your table and index statistics are up-to-date. If you still feel that Oracle processes it badly, try playing on the optimizer goal (FIRST_ROWS/ALL_ROWS) and if you get a result which satisfies you add it as a hint.


SF

>----- ------- Original Message ------- -----
>From: New DBA <[EMAIL PROTECTED]>
>To: Multiple recipients of list ORACLE-L
><[EMAIL PROTECTED]>
>Sent: Tue, 23 Sep 2003 23:39:44
>
>
>Hi All,
>
>I need help in tuning the following query. It takes
>around 6-7 minutes to run. I hope that someone will
>be able to go through the details and give me a few
>pointers.
>
>I have gathered a few statistics, but don't know
>where to go from here.
>
>Please view the mail in a fixed size font e.g.
>courier to preserve the formatting. If the lines
>wrap over copying and pasting in a text editor
>might help, though I'm not sure.
>
>I apologize for the long message in advance.
>
>Following is the query:
>
>SELECT  UNIQUE
> MEPAI.MPAI_NAV_MOD ,
> MEPAI.MPAI_NAV_MODS,
> MEPAI.MPAI_SYS_NO,
> MEPAI.MPAI_PAI_SYS_NO,
> MEPAI.MPAI_AS_OF_DATE,
> PRODUCTS.ISS_INSTR_ID PRODUCT_INSTR_ID,
> CUR.CUR_CURRENCY_NAME,
> CUR.CUR_CURRENCY_CODE,
> CUR.CUR_SYS_NO
>FROM
> EPR_CURRENCIES                        CUR,
> EPR_GEOGRAPHIES                       GEO,
> EPR_PRODUCTS                          PRODUCTS,
> MOD_EPR_PRICING_ASSET_INFO            MEPAI
>WHERE  MEPAI.MPAI_ISS_SYS_NO   =
>PRODUCTS.ISS_SYS_NO
>AND MEPAI.MPAI_GEO_SYS_NO   = GEO.GEO_SYS_NO
>AND MEPAI.MPAI_CUR_SYS_NO   = CUR.CUR_SYS_NO
>AND MEPAI.MPAI_AS_OF_DATE IN
> (
>   to_date('03/01/2003','MM/DD/YYYY'),
>to_date('03/02/2003','MM/DD/YYYY')
> , to_date('03/03/2003','MM/DD/YYYY'),
>to_date('03/04/2003','MM/DD/YYYY')
> , to_date('03/05/2003','MM/DD/YYYY'),
>to_date('03/06/2003','MM/DD/YYYY')
> , to_date('03/07/2003','MM/DD/YYYY'),
>to_date('03/08/2003','MM/DD/YYYY')
> , to_date('03/09/2003','MM/DD/YYYY'),
>to_date('03/10/2003','MM/DD/YYYY')
> , to_date('03/11/2003','MM/DD/YYYY'),
>to_date('03/12/2003','MM/DD/YYYY')
> , to_date('03/13/2003','MM/DD/YYYY'),
>to_date('03/14/2003','MM/DD/YYYY')
> , to_date('03/15/2003','MM/DD/YYYY'),
>to_date('03/16/2003','MM/DD/YYYY')
> , to_date('03/17/2003','MM/DD/YYYY'),
>to_date('03/18/2003','MM/DD/YYYY')
> , to_date('03/19/2003','MM/DD/YYYY'),
>to_date('03/20/2003','MM/DD/YYYY')
> , to_date('03/21/2003','MM/DD/YYYY'),
>to_date('03/22/2003','MM/DD/YYYY')
> , to_date('03/23/2003','MM/DD/YYYY'),
>to_date('03/24/2003','MM/DD/YYYY')
> , to_date('03/25/2003','MM/DD/YYYY'),
>to_date('03/26/2003','MM/DD/YYYY')
> , to_date('03/27/2003','MM/DD/YYYY'),
>to_date('03/28/2003','MM/DD/YYYY')
> , to_date('03/29/2003','MM/DD/YYYY'),
>to_date('03/30/2003','MM/DD/YYYY')
> , to_date('03/31/2003','MM/DD/YYYY')
> )
>AND PRODUCTS.ISS_INSTR_ID in
>(1321,1339,1344,1342,1343,1341,1340)
>AND CUR.CUR_SYS_NO in (200,226)
>Order By MEPAI.MPAI_SYS_NO
>
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Stephane Faroult
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Justin Cave Distributed Database Consulting

--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Justin Cave
 INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to