Re: Slow UPDATE

From: Terry Sutton <terrysutton_at_usa.net>
Date: Tue, 18 May 2004 09:23:32 -0700
Message-ID: <016501c43cf4$b4a649a0$0400a8c0@TerrySutton>

In Thomas' original post, he included the tkprof explain plan, but not the Row Source Operation. The explain plan claims that the unique key is being used, but the wait events show clearly that full scans are occurring.

The Row Source Operation info is the one to rely on to determine what actually happened during the trace.

--Terry

Original Message ----- From: "Bobak, Mark" <Mark.Bobak_at_il.proquest.com> To: <oracle-l_at_freelists.org> Sent: Tuesday, May 18, 2004 8:30 AM Subject: RE: Slow UPDATE

Note that regardless of whether the EXPLAIN=3D option is passed to tkprof, the execution plan from the STAT lines in the tracefile will be reported under "Row Source Operation" in the tkprof=20 output. If EXPLAIN=3D option is specified, then in addition to "Row Source Operation", you'll have "Execution Plan" followed by the explain plan that was executed at tkprof runtime, using the userid/password specified.

-Mark

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

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Tanel P=F5der Sent: Tuesday, May 18, 2004 11:12 AM
To: oracle-l_at_freelists.org
Subject: Re: Slow UPDATE

But if you don't specify EXPLAIN=3D option then tkprof will read the execution plans directly from STAT lines in the tracefile.=20

...some stuff deleted....

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.
--

Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html

Please see the official ORACLE-L FAQ: http://www.orafaq.com

Received on Tue May 18 2004 - 11:22:47 CDT