等待事件--db file sequential reads
等待事件--db file sequential reads
Possible Causes
Use of an unselective index
Fragmented Indexes
High I/O on a particular disk or mount point
Bad application design
Index reads performance can be affected by slow I/O subsystem and/or poor database files layout, which result in a higher average wait time
Actions
Check indexes on the table to ensure that the right index is being used
Check the column order of the index with the WHERE clause of the Top SQL statements
Rebuild indexes with a high clustering factor
Use partitioning to reduce the amount of blocks being visited
Make sure optimizer statistics are up to date
Relocate ‘hot’ datafiles
Consider the usage of multiple buffer pools and cache frequently used indexes/tables in the KEEP pool
Inspect the execution plans of the SQL statements that access data through indexes
Is it appropriate for the SQL statements to access data through index lookups?
Is the application an online transaction processing (OLTP) or decision support system (DSS)?
Would full table scans be more efficient?
Do the statements use the right driving table?
The optimization goal is to minimize both the number of logical and physical I/Os.
Remarks
The Oracle process wants a block that is currently not in the SGA, and it is waiting for the database block to be read into the SGA from disk.
Significant db file sequential read wait time is most likely an application issue.
If the
DBA_INDEXES.CLUSTERING_FACTOR of the index approaches the number of blocks in the table, then most of the rows in the table are ordered. This is desirable.
However, if the clustering factor approaches the number of rows in the table, it means the rows in the table are randomly ordered and thus it requires more I/Os to complete the operation. You can improve the index’s clustering factor by rebuilding the table so that rows are ordered according to the index key and rebuilding the index thereafter.
The OPTIMIZER_INDEX_COST_ADJ and OPTIMIZER_INDEX_CACHING initialization parameters can influence the optimizer to favour the nested loops operation and choose an index access path over a full table scan.
Tuning I/O related waits Note# 223117.1
db file sequential read Reference Note# 34559.1
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/24996904/viewspace-767590/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 等待事件--db file scattered reads事件
- db file sequential read等待事件事件
- 【等待事件】db file sequential read事件
- 詳解 db file sequential read 等待事件事件
- 【TUNE_ORACLE】等待事件之IO等待“db file sequential read”Oracle事件
- oracle之 db file sequential read等待事件優化思想Oracle事件優化
- 何時會發生db file sequential read等待事件?事件
- db file sequential read wait event等待事件之二AI事件
- 等待事件db file sequential read、db file scattered read和direct read的區別事件
- 【kingsql分享】何時出現生db file sequential read等待事件SQL事件
- control file sequential read等待事件事件
- db file sequential read事件的發生事件
- db file scattered read等待事件事件
- 【等待事件】db file scattered read事件
- oracle等待事件2構造一個DB File Sequential Read等待事件和構造一個Direct Path ReadOracle事件
- db file scattered read與事件db file sequential read相類似(轉)事件
- 【TUNE_ORACLE】等待事件之IO等待“db file parallel write”Oracle事件Parallel
- db file sequential read 詳解
- 【TUNE_ORACLE】等待事件之IO等待“db file scattered read”Oracle事件
- db file async I/O submit 等待事件優化MIT事件優化
- db file async I/O submit 等待事件說明MIT事件
- 解決db file sequential read與db file scattered read
- db file sequential read及優化優化
- 0322理解db file parallel read等待事件2Parallel事件
- 0316理解db file parallel read等待事件Parallel事件
- 非空閒的等待事件-db file scattered read事件
- Oracle db file parallel write 和 log file parallel write 等待事件 說明OracleParallel事件
- I/O上的等待事件 —— control file sequential read/control file parallel write事件Parallel
- High Waits on 'Db File Sequential Read'AI
- data file int write和db file sequential read個人想法
- db file async I/O submit等待事件的故障診斷MIT事件
- 非空閒等待事件之:db file scattered read(轉)事件
- Waiting Too Frequently for 'db file sequential read'AI
- oracle wait event之db file sequential readOracleAI
- log file sync等待事件事件
- 【等待事件】log file sync事件
- LOG FILE SWITCH等待事件事件
- log file sync" 等待事件事件