TIMED_STATISTICS = true

2. Restart your database. 
3. Run your application.
4. Run tkprof against the tracefile created by your application:

tkprof EXPLAIN=username/passwd

5. Look at formatted output of trace command and make sure that your

      SQL statement is using indexes correctly.  Refer to DBA guide for a list

      of rules that the oracle optimizer uses when choosing a path for a SQL statement. 

                 <<<<<< OUTPUT OF TKPROF FILE >>>>>>> 

count   = number of times OPI procedure was executed 

cpu     = cpu time executing in hundredths of seconds 

elap    = elapsed time executing in hundredths of secs 

phys    = number of physical reads of buffers (from disk) 

cr      = number of buffers gotten for consistent read 

cur     = number of buffers gotten in current mode (usually for update) 

rows    = number of rows processed by the OPI call 

===========================================================

select * from emp where empno=7369  

            count     cpu    elap    phys      cr     cur    rows 

Parse:          1       0       0       0       0       0 

Execute:        1       0       0       0       0       2       0 

Fetch:          1       0       0     219     227       0       2 

Execution plan: 

TABLE ACCESS (FULL) OF EMP 

===========================================================

select empno from emp where empno=7934  

            count     cpu    elap    phys      cr     cur    rows 

Parse:          2       0       0       0       0       0 

Execute:        2       0       0       0       0       2       0 

Fetch:          2       0       0       0&nb

监控Oracle数据库的常用shell脚本 Raw Partitions and Windows NT

设为首页 | 加入收藏 | 关于我们 | 联系我们 | 广告服务 | 网站地图 | 友情链接 | 在线帮助 | 免责声明 Sitemap W3school

如果您觉得本站不错，别忘了告诉您的同学和同事哟 ^_^

欢迎各网站转载我们的原创，转载时请注明出处。

All copyright is reserved by 软晨网（RuanChen.com）