QUESTION 45-DB_FILE_MULTIBLOCK_READ_COUNT

You notice a high number of waits for the db file scattered read and db file sequential read events in the recent Automatic Database Diagnostic Monitor (ADDM) report. After further investigation, you find that queries are performing too many full table scans and indexes are not being used even though the filter columns are indexed. Identify three possible reasons for this.
A. Missing or stale histogram statistics
B. Undersized shared pool
C. High clustering factor for the indexes
D. High value for the DB_FILE_MULTIBLOCK_READ_COUNT parameter
E. Oversized buffer cache
Correct Answer: ACD

您注意到，在最近的自动数据库诊断监视器(ADDM)报告中，对db文件分散读取和db文件顺序读取事件的等待次数很高。经过进一步的调查，您发现查询执行了太多的全表扫描，并且没有使用索引，即使对筛选器列进行了索引。找出三个可能的原因。

A.缺少或陈旧的直方图统计信息

B.共享池太小

C.各指标聚类系数高

D.DB_FILE_MULTIBLOCK_READ_COUNT参数的高值

E.超大缓冲区缓存

正确答案:ACD

 

D: DB_FILE_MULTIBLOCK_READ_COUNT是在表扫描期间可以用来最小化I/O的参数之一。它指定在顺序扫描期间一个I/O操作中读取的最大块数。执行全表扫描所需的总I/ o数取决于表的大小、多块读计数以及操作是否使用并行执行等因素。