RE: 10g slowdown

From: Blanchard William <William.Blanchard_at_kohler.com>
Date: Fri, 12 Dec 2008 09:08:07 -0600
Message-ID: <AD7C091172665E4387E4EBA18BFE01F0088C58A8@USWIMS03.kohlerco.com>


SELECT STATEMENT
  NESTED LOOPS

OUTER             1
    TABLE ACCESS                        ZKPACDATA                    BY
INDEX ROWID    1
      Filter Predicates
        AND
          T_00.WERKS='MS'
          T_00.LOEKZ<>'X'
      INDEX                             ZKPACDATA~Z1
RANGE SCAN        1
        Access Predicates
          AND
            T_00.MANDT='010'
            T_00.AUFNR='000012284021'
            T_00.VORNR='6100'
      INDEX                             ZKPACREASONCODES~0
UNIQUE SCAN       0
        Access Predicates
          AND
            T_01.WERKS(+)='MS'
            T_01.REASONCODE=T_01.REASONCODE(+)



William

-----Original Message-----

From: Bobak, Mark [mailto:Mark.Bobak_at_proquest.com] Sent: Friday, December 12, 2008 9:00 AM
To: Blanchard William; Jack van Zanen
Cc: oracle-l_at_freelists.org
Subject: RE: 10g slowdown

Can you post the execution plan?



From: oracle-l-bounce_at_freelists.org [oracle-l-bounce_at_freelists.org] On Behalf Of Blanchard William [William.Blanchard_at_kohler.com] Sent: Friday, December 12, 2008 9:56 AM
To: Jack van Zanen
Cc: oracle-l_at_freelists.org
Subject: RE: 10g slowdown

The query is technically on one table. It uses a join as a filter only. The table is 5.1 million rows (~3.4G) and stays relatively constant.

SELECT t_00.uname, t_00.erdat, t_00.aezeit, t_00.kpackey, t_00.trantype, t_00.lmnga

    FROM sapr3.zkpacdata t_00, sapr3.zkpacreasoncodes t_01     WHERE (t_00.reasoncode = t_01.reasoncode(+)

                AND t_00.werks = t_01.werks(+))
        AND t_00.mandt = '010'
        AND t_00.loekz <> 'X'
        AND t_00.vornr = '6100'
        AND t_00.aufnr = '000012284021'
        AND t_00.werks = 'MS'

This query took 4.5 hours. When I run an explain plan the cost is 1. That's why I'm confused. My initial thought was that there was something locking the table but even that wouldn't necessarily explain the 4.5 hours. The program was run again during a maintenance window and it still took 6 hours.

William



From: jack.van.zanen_at_gmail.com [mailto:jack.van.zanen_at_gmail.com] On Behalf Of Jack van Zanen
Sent: Thursday, December 11, 2008 10:17 PM To: Blanchard William
Cc: oracle-l_at_freelists.org
Subject: Re: 10g slowdown

are you saying that a query on a single table takes 6 hours?

How big is the table in GB/TB?

Jack

2008/12/12 Blanchard William
<William.Blanchard_at_kohler.com<mailto:William.Blanchard_at_kohler.com>>

We have a query that began taking a long time about a week ago. The program, in SAP, ran for 10 - 15 minutes but is now taking about 6 hours. The table has 5.1 million rows. The explain plan shows a simple index range scan. We just reran statistics on the table and all indexes but no luck We are concentrating on the one query that took about 4.75 hours.

Does anyone see something glaring or know of a simple test to locate the problem?

Let me know if you need any other info.

Thank you,

William B.

--

J.A. van Zanen

--

http://www.freelists.org/webpage/oracle-l Received on Fri Dec 12 2008 - 09:08:07 CST

Original text of this message