Figure 5-10. This classic OSM time interval wait event report shows the top wait event db file scattered read having an average wait time of 0.6 ms. Does this represent an IO bottleneck? Not unless you think a multiblock read request taking 0.6 ms is a problem.

So is there any IO subsystem bottleneck? Clearly, the IO subsystem capacity has exceeded Oracle's IO read requirements, which means there is not an IO bottleneck. But this in no way implies there is not a problem. If users are unsatisfied with application performance, you will probably be able to discover Oracle-focused, operating system-focused, and application-focused solutions, such as the following:

* Oracle focused: If the desired block had been found in the Oracle buffer cache, Oracle would not have asked the operating system for the block. Therefore, a larger Oracle buffer cache would reduce the likelihood of a db file scattered read. Of course, there needs to be both memory available and CPU available to manage the increased buffer cache. Other possibilities are using the keep or recycle pools, or other Oracle instance-focused solutions to increase the likelihood of the block being found in Oracle's buffer cache.