We shall see the below output and understand each bit of information of it one by one:
select *
from
tab
call count cpu elapsed disk query current rows
------- ------ -------- ---------- ---------- ---------- ---------- ----------
Parse 3 0.00 0.00 0 0 0 0
Execute 3 0.00 0.00 0 0 0 0
Fetch 6 0.04 0.04 21 1884 0 6
------- ------ -------- ---------- ---------- ---------- ---------- ----------
total 12 0.04 0.04 21 1884 0 6
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 54
Rows Row Source Operation
------- ---------------------------------------------------
2 NESTED LOOPS OUTER (cr=628 pr=21 pw=0 time=25030 us)
2 TABLE ACCESS FULL OBJ$ (cr=621 pr=20 pw=0 time=21996 us)
2 TABLE ACCESS CLUSTER TAB$ (cr=7 pr=1 pw=0 time=3051 us)
2 INDEX UNIQUE SCAN I_OBJ# (cr=4 pr=1 pw=0 time=3033 us)(object id 3)
Library Cache Misses in TKPROF: TKPROF also lists the number of library cache misses resulting from parse and execute steps for each SQL statement.
Deciding Which Statements to Tune:
You need to find which SQL statements use the most CPU or disk resource.
Also a large gap between CPU and elapsed timings indicates Physical I/Os.
Enjoy:-)
4 comments:
ugg boots
michael kors handbags outlet
christian louboutin shoes
hermes belts
fitflops
oakley sunglasses
michael kors uk
ralph lauren
nike outlet
nike roshe
balenciaga shoes
vans shoes
calvin klein outlet online
pandora jewelry
louboutin shoes
lebron 16
westbrook shoes
off white jordan 1
adidas tubular
hogan outlet online
replica bags blog replica bags blog replica bags near me
imp source bags replica gucci great site louis vuitton replica our website replica designer bags wholesale
Post a Comment