Understanding automatically tuned multi-block reads

Question: I did play around with different settings of db_file_multiblock_read_count within 10g with no appreciable results. My setting of the db_file_multiblock_read_count parameter had almost no effect on query performance, I guess this is related to a read ahead cache on os/filesystem/disk device level with at least 128 blocks.

 I am concerned about switching to sequential reads with setting db_file_multiblock_read_count=0, using the new 10g feature "Automatically Tuned Multiblock Reads".

Is it already reliable to use "Automatically Tuned Multiblock Reads" with 10g or should one still run with an as high as possible setting for db_file_multiblock_read_count? Are there any drawbacks having db_file_multiblock_read_count on a high value ?

Find the answer to this question and more information on automatically tuned multi-block reads here:



Need a Health Check?

Oracle is the worlds most complex and robust database and there are hundreds of sub-optimal setting that can cripple your database performance.

Burleson Consulting has a great Oracle health check where we identify all database bottlenecks to ensure that your mission-critical system is running at optimal speeds.

Just call 800-766-1884 to schedule your health check.


Need Oracle Training?

The very best Oracle training comes from Burleson Consulting, where you get an on-site visit by an experienced Oracle expert and author.  Whether it's one-on-one mentoring or getting a customized on-site Oracle training class, there is no substitute for BC Oracle training.  Just call 800-766-1884 for details, and check-out our on-site Oracle training catalog at the following link: