Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: CBO irregularity
There are at least three reasons:
Check your trace data. You'll probably find that many of your multi-block read calls are nowhere near the size that you've specified in your db_file_multiblock_read_count parameter.
For more details, see Jeff Holt's "Predicting multi-block read call sizes" at www.hotsos.com/e-library.
Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com
Nullius in verba
Upcoming events:
- Performance <http://www.hotsos.com/courses/PD101.php> Diagnosis 101: 6/22
Pittsburgh, 7/20 Cleveland, 8/10 Boston
- SQL Optimization <http://www.hotsos.com/courses/OP101.php> 101: 5/24 San
Diego, 6/14 Chicago, 6/28 Denver
- Hotsos Symposium 2005: March 6-10 Dallas
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
On Behalf Of Naveen, Nahata (IE10)
Sent: Tuesday, June 08, 2004 1:39 AM
To: oracle-l_at_freelists.org
Subject: RE: CBO irregularity
Thanx Cary and Satheesh,
Why wud the no. of blocks read be less than DB_FILE_MULTBLOCK_READ_COUNT?
Is it dependent on the I/O sub-system?
Regards
Naveen
True. The Oracle kernel also collects this information when you use dbms_stats.gather_database_stats.
-- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------Received on Tue Jun 08 2004 - 01:49:53 CDT
![]() |
![]() |