Re: Laying out Oracle on a SAN

If you have an existing environment and would like to go SAN. I would first get the IO requirements of the peak and low workloads. I would get the following requirements:

• Read and Write IOPS
• Redo IOPS
• Read and Write MB/s
• Redo MB/s

I would use the script here
http://karlarao.wordpress.com/2010/01/31/workload-characterization-using-dba_hist-tables-and-ksar/ to gather those info.

Then, I would discuss the numbers with the SAN storage engineer.. and speak about the SAN capacity in terms of IOPS and MB/s and work with him on how would I achieve the IO requirements of my database.

Then, I would validate the SAN environment by running Orion, or actually running the workload.

BTW, I recommend you also read this paper by Krishna Manoharan.  "Storage Design for Datawarehousing" presentation http://sites.google.com/site/docsfordownload/files/StorageDesignforDatawarehousingv8.pdf?attredirects=0

Bottom line, your IO capacity should be able to handle your IO requirements... be it RAID5 or RAID 10...

• Karl Arao karlarao.wordpress.com

On Sat, Feb 6, 2010 at 2:25 PM, Douglas Cowles <dcowles_at_us.ibm.com> wrote:
>
> Looking for tips as to laying out an Oracle DB on a SAN. � I assume you probably want the fastest I/O for the redo logs and temp?
> The �SAN I am working with has LUNS are carved up out of 10 or so disks on RAID5. � Does it matter if we put the archive logs and the datafiles on the same LUN? �Are these kinds of questions better suited to the SAN expert? �Assuming I can defer a lot to the SAN expert, what I/O requirements and path requirements should I provide them? � Centralized storage is centralized storage so I'm not sure how to parse things out. � �I also realize a lot of this may depend on the kind of SAN and its particular characteristics, but are there generic rules that can be provided?
>
> Doug C

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