Top 5 Timed Foreground Events
Event | Waits | Time(s) | Avg wait (ms) | % DB time | Wait Class |
---|---|---|---|---|---|
SQL*Net vector data from client | 5,217 | 1,294 | 248 | 3118.53 | Network |
DB CPU | 20 | 48.84 | |||
db file sequential read | 15,171 | 11 | 1 | 27.49 | User I/O |
control file sequential read | 22,860 | 9 | 0 | 21.51 | System I/O |
ARCH wait on c/f tx acquire 2 | 1 | 1 | 977 | 2.35 | Other |
SQL*Net vector data from client:这个不懂
DB CPU:是CPU的空闲等待时间。
db file sequential read:相对于scattered read一次读入多个block,sequential read一次进行单个块的读取,联系到执行计划可以得出sequential read一般发生在进行索引扫描时(当然有的全表扫描也可能发生),主要从index,rollback(or undo) segments, tables(通过rowid访问表),control files和data file headers中进行single-block read.,而scattered read一般发生在全表扫描。因此针对db file sequential read等待过高的情况可以从索引的角度进行分析。
control file sequential read:对单个控制文件I/O 存在问题时,这两个事件会出现。如果等待比较明显,检查单个控制文件,看存放位置是否存在I/O 瓶颈。
ARCH wait on c/f tx acquire 2:这个不懂
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/10322123/viewspace-610878/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/10322123/viewspace-610878/