RE: Laying out Oracle on a SAN
- From: William Muriithi <william.muriithi@xxxxxxxxxxxxxxxxxxx>
- To: "dcowles@xxxxxxxxxx" <dcowles@xxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Sat, 6 Feb 2010 10:41:04 -0600
Doug
If the SAN people are flexible enough and as you hinted below, you are worried
about IO through put, you should use RAID 10 instead of RAID 5. A little bit
faster but with a bit more space lost. Now, that may still be cheaper than
special arrangements to improve IO for redo logs and temp
William
________________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx [oracle-l-bounce@xxxxxxxxxxxxx] On Behalf
Of Douglas Cowles [dcowles@xxxxxxxxxx]
Sent: Saturday, February 06, 2010 1:25 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Laying out Oracle on a SAN
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
Other related posts: