Re: ASM parameters
Date: Fri, 25 Jan 2008 03:43:42 -0800 (PST)
On Jan 25, 3:46 am, Mladen Gogala <mgog..._at_yahoo.com> wrote:
> 10.2.0.3 on RH Linux 4.0, update 4, 2 node RAC. I am experimenting with
> ASM parameters, DB_CACHE_SIZE and DB_FILE_MULTIBLOCK_READ_COUNT.
> Default cache size is 25M, MBRC is 110. Default block size is 4k.
> I have set cache size to 128M, MBRC to 256 (1M reads). I tried going above
> 1M, but the parameter was ignored. RMAN seems to work much faster,
> benchmark is in progress. Does anybody have any recommendations or
> experiences to share?
> Mladen Gogalahttp://mgogala.freehostia.com
I don't use ASM, but there may be some hints provided in "Cost-Based
Oracle Fundamentals" to explain what you are seeing. Paraphrased from
Oracle uses MBRC from the SYS.AUX_STATS$ for cost calculations, but the runtime engine tries to use DB_FILE_MULTIBLOCK_READ_COUNT when performing physical reads. On Start up, Oracle determines the operating system's largest physical read size and silently uses that to limit whatever value is set for DB_FILE_MULTIBLOCK_READ_COUNT.
You might also want to take a look at the following regarding the DB_FILE_MULTIBLOCK_READ_COUNT parameter: http://jonathanlewis.wordpress.com/2007/05/20/system-stats-strategy/
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc. Received on Fri Jan 25 2008 - 05:43:42 CST