RE: db_file_multiblock_read_count causing full scans to takelonger?

  • From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
  • To: <kevin.lidh@xxxxxxxxx>, <don@xxxxxxxxx>, "Christian Antognini" <Christian.Antognini@xxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
  • Date: Tue, 19 Dec 2006 13:38:21 -0700

Am I missing something, or isn't it best to just leave this parameter
unset (default) in 10.2, in which case Oracle will automatically adjust
it to the max io size of your OS?  Along with computing system stats on
a typical workload so you have an accurate mbrc, you should get the best
of both worlds - accurate costing and optimized sequential scans, right?

I have it unset on my 10.2 AIX 5.3 system and it has defaulted to 128
with an 8k block size (1MB).


Privileged/Confidential Information may be contained in this message or 
attachments hereto. Please advise immediately if you or your employer do not 
consent to Internet email for messages of this kind. Opinions, conclusions and 
other information in this message that do not relate to the official business 
of this company shall be understood as neither given nor endorsed by it.


Other related posts: