| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.misc -> Interpreting an SQL Trace file
All,
Below is output from an SQL Trace of a query in one of our batch jobs. How do I interpret the EXPLAIN PLAN output? Why were there 93000 rows accessed by ROWID, but only one accessed during the UPDATE. We are using Oracle 7.1.6 on HP-UX.
In the past, I've posted quite a few questions on interpreting SQL Trace output. How much of the problems I am having interpreting the output stem from using an older version of Oracle, where the trace facility, or at least TKPROF might have some bugs? Would I perhaps get better results upgrading to Oracle 7.3? Just wondering...
Please email me as well as responding to the newsgroup.
Thanks,
Brian
SELECT ROWID,PART_NBR,RESIDENT_SITE,PART_DESC,PART_TYPE,PLAN_CODE,
...
AUTO_OPN_EXC_IND,AUTO_CLS_EXC_IND,FREQ_OF_REPAIR
INTO:b1,:b2,:b3,:b4,:b5,
...
:b110,:b111,:b112,:b113,:b114
FROM
PART WHERE PART_NBR=:b2 FOR UPDATE NOWAIT
call count cpu elapsed disk query current rows
Parse 12 0.07 0.12 0 0 0 0 Execute 806 126.99 140.49 390095 406248 3245 794 Fetch 806 3.24 3.67 9321 9595 76 19
total 1624 130.30 144.28 399416 415843 3321 813
Misses in library cache during parse: 1
Optimizer hint: CHOOSE
Parsing user id: 20 (CSIUSER)
Rows Execution Plan
------- ---------------------------------------------------
0 SELECT STATEMENT HINT: CHOOSE
1 FOR UPDATE
93000 TABLE ACCESS (BY ROWID) OF 'PART'
0 INDEX (UNIQUE SCAN) OF 'PART_PK' (UNIQUE)
--
Brian M. Biggs mailto:bbiggs_at_cincom.com
Cincom Systems, Inc. voice: (513) 677-7661
http://www.cincom.com/
Received on Mon Nov 18 1996 - 00:00:00 CST
 |
 |