Re: General SAN advice needed for 2TB 9.2.0.8 database on HP-UX

> Just some more notes to confirm that I have this correct.
>
> Stripe depth is the size of the stripe, sometimes called stripe unit.
> Stripe width is the product of the stripe depth and the number of
> drives in the striped set.http://download.oracle.com/docs/cd/B28359_01/server.111/b28274/iodesi...
>
> segment size = stripe depth
> 1MB stripe width = eight drives * stripe depth = 8 * 128KB
>
> This SAN parameter is dynamic apparently (guess it depends on brand)
> SAN Cache block size = SAN cache page size = DB_BLOCK_SIZE = 8KB
> DB_BLOCK_SIZE should = file block size which should = cache block
> sizehttp://www.emc.com/collateral/hardware/white-papers/h796-implementing...
>
> We probably don't need to worry about making the log files non-cached
> as the cache is battery backed up?

Your messed up if you can't depend on the cache of your storage array.

Most of my experience with Oracle systems has been setting up OLTP ( not big datawarehouse ) systems.

I almost always separate out the disks for online logs from the rest of the system. For commit happy systems I really want to have average log file sync times at 1 ms or under if I can.

These days my systems are using ASM but I still setup separate diskgroups for the online log files and separate the disks and that stuff out. Received on Thu Jun 24 2010 - 08:23:09 CDT