Re: system stats and db_file_multi_block_read_count

From: goran bogdanovic <goran00_at_gmail.com>
Date: Mon, 15 Aug 2011 00:18:29 +0200
Message-ID: <CAGyPXK4hruUaLQkjkTCqBWAaSh4mZNxso+fw=HH_wNZqDnc9SQ_at_mail.gmail.com>

during database startup oracle negotiates with the operating system what is largest physical read size supported and uses that value for the db_file_multiblock_read_count.
The other points has been already addresed by Nail.

regards,
goran

On Sat, Aug 13, 2011 at 4:44 PM, Neil Chandler <neil_chandler_at_hotmail.com>wrote:

> That depends upon your requirements. I would start with it not set and see
> if it fits your requirements. It will then implicitly set the value to the
> highest possible for your I/O system - probably 128. However, that is NOT
> the same as setting 128 explicitly. If reasonable for your system, use the
> defaults.
>
> Be careful when collecting system stats, given the global change that it
> makes. You also need to think carefully about when to gather the stats
> depending upon the workload going through the system - during OLTP? Batch?
> Data Loading? They may all give different answers.
>
> You should also consider gathering system stats with the same level of
> change control that you apply to your application code, and test the stats
> in UAT before applying to Production.
>
> regards
>
> Neil Chandler
>
> ------------------------------
> Date: Sat, 13 Aug 2011 04:16:45 +0100
> From: hrishys_at_yahoo.co.uk
> Subject: system stats and db_file_multi_block_read_count
> To: oracle-l_at_freelists.org
>
>
> Hi
>
> Do i need to set the value for db_file_multi_block_read_count explicitly if
> we collect system stats manually on 10g ?
>
> regards
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Sun Aug 14 2011 - 17:18:29 CDT