| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> c.d.o.server -> Re: Help interpreting TKPROF output
[ snip ]
> Rows Row Source Operation
> ------- ---------------------------------------------------
> 0 FILTER
> 1 FILTER
> 1745637 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 NESTED LOOPS OUTER
> 873290 TABLE ACCESS FULL S_EVT_ACT
> 770325 TABLE ACCESS BY INDEX ROWID S_ASSET
> 1643614 INDEX UNIQUE SCAN (object id
> 163988)
> 869748 TABLE ACCESS BY INDEX ROWID
> S_CONTACT
> 1743037 INDEX UNIQUE SCAN (object id
> 165128)
> 869748 TABLE ACCESS BY INDEX ROWID S_CONTACT
> 1743037 INDEX UNIQUE SCAN (object id 165122)
> 2395 TABLE ACCESS BY INDEX ROWID S_LANG
> 875684 INDEX UNIQUE SCAN (object id 168360)
> 770256 TABLE ACCESS BY INDEX ROWID S_PROD_INT
> 1643545 INDEX UNIQUE SCAN (object id 170462)
> 0 TABLE ACCESS BY INDEX ROWID
> S_ACT_PROD_APPL
> 873289 INDEX UNIQUE SCAN (object id 163543)
> 0 TABLE ACCESS BY INDEX ROWID S_PROD_INT
> 873289 INDEX UNIQUE SCAN (object id 170462)
> 869748 TABLE ACCESS BY INDEX ROWID S_CONTACT
> 1743037 INDEX UNIQUE SCAN (object id 165128)
> 872359 TABLE ACCESS BY INDEX ROWID S_CONTACT
> 1745648 INDEX UNIQUE SCAN (object id 165128)
> 0 TABLE ACCESS BY INDEX ROWID S_EVT_ACT
> 873289 INDEX UNIQUE SCAN (object id 166898)
> 0 TABLE ACCESS BY INDEX ROWID S_PROJ
> 873289 INDEX UNIQUE SCAN (object id 170716)
> 513307 TABLE ACCESS BY INDEX ROWID S_CONTACT
> 1386596 INDEX UNIQUE SCAN (object id 165128)
> 0 TABLE ACCESS BY INDEX ROWID S_PROJITEM
> 873289 INDEX UNIQUE SCAN (object id 170731)
> 839750 TABLE ACCESS BY INDEX ROWID S_OPTY
> 1713039 INDEX UNIQUE SCAN (object id 168882)
> 39271 TABLE ACCESS BY INDEX ROWID S_STG
> 912560 INDEX UNIQUE SCAN (object id 172136)
> 5 TABLE ACCESS BY INDEX ROWID S_ORG_EXT
> 873294 INDEX UNIQUE SCAN (object id 169420)
> 871010 TABLE ACCESS BY INDEX ROWID S_ACT_EMP
> 1747897 INDEX RANGE SCAN (object id 174811)
> 870996 TABLE ACCESS BY INDEX ROWID S_CONTACT
> 1744285 INDEX UNIQUE SCAN (object id 165128)
> 870996 INDEX UNIQUE SCAN (object id 169766)
> 170 TABLE ACCESS BY INDEX ROWID S_EVT_MAIL
> 873459 INDEX RANGE SCAN (object id 167006)
> 0 TABLE ACCESS BY INDEX ROWID S_EVT_ACT_SS
> 873289 INDEX RANGE SCAN (object id 166977)
> 31 TABLE ACCESS BY INDEX ROWID S_SRV_ACT
> 873320 INDEX RANGE SCAN (object id 171966)
> 809443 TABLE ACCESS BY INDEX ROWID S_OPTY_X
> 1682732 INDEX RANGE SCAN (object id 169153)
> 1744696 INDEX RANGE SCAN (object id 169797)
> 0 FILTER
> 0 NESTED LOOPS OUTER
> 0 NESTED LOOPS
> 0 NESTED LOOPS
> 0 INDEX RANGE SCAN (object id 169071)
> 0 INDEX UNIQUE SCAN (object id 169766)
> 0 TABLE ACCESS BY INDEX ROWID S_POSTN
> 0 INDEX UNIQUE SCAN (object id 170114)
> 0 TABLE ACCESS BY INDEX ROWID S_CONTACT
> 0 INDEX UNIQUE SCAN (object id 165128)
>
>
[snip]
The biggest [problem here is (get ready for it ...) **IO**. This query appears to be visiting too many rows.
What waits are being generated when this is executing? What kind of sar output do you have?
What did it do before?
-- Ron Reidy Oracle DBAReceived on Fri Nov 07 2003 - 19:18:06 CST
![]() |
![]() |