RE: Laying out Oracle on a SAN
- From: Josh Collier <Josh.Collier@xxxxxxxxxxxx>
- To: "dcowles@xxxxxxxxxx" <dcowles@xxxxxxxxxx>
- Date: Sat, 6 Feb 2010 10:24:28 -0800
If you really work for IBM you should be able to get this information from your
partnership with netapp :)
on the other hand, how many filer do you have? What type of SAN is it?
Here is something I got from an ibm doc, we have a ibm N-series which is
basically a netapp. I like to keep my binaries on local disk. We mount these
on the FC protocol.
Table 3-1 Recommended FlexVol volumes and aggregates layout
Oracle database files Recommended layout Comments
Database binaries Dedicated FlexVol volume
Database config files Dedicated FlexVol volume Multiplex with
Transaction logs (such as control files)
Transaction log files Dedicated FlexVol volume Multiplex with
Database config files (redo logs, we have 2 flexvol for redo, one on each
filer), 2 different aggregates.
Archive logs Dedicated FlexVol volume Use
SnapMirror(r) feature
Data files Dedicated FlexVol volume, on my larger
systems I have several of these, as our version of SDU has a 1TB limit on
solaris
Temporary datafiles Dedicated FlexVol volume Do not make Snapshot
copies of this volume
We have found it expedient for making flexclones on the n-series to name our
mounts like this
/dbname_data_01
And put the data directly underneath with no other directory structure, this
makes flexclones less problematic.
If you do have a n-series, be sure not to mix file types, as this will muck up
the flexcloning too. Preventing a snaprestore (fast) and requiring a mounting
of the snapshot and a copy to the destination (slow on a multi-TB DW)
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Douglas Cowles
Sent: Friday, February 05, 2010 10:25 PM
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
Other related posts:
