Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: best raid configuration for oracle on solaris

Re: best raid configuration for oracle on solaris

From: Niall Litchfield <n-litchfield_at_audit-commission.gov.uk>
Date: Sat, 21 Jul 2001 21:35:54 GMT
Message-ID: <3b4efd55$0$3759$ed9e5944@reading.news.pipex.net>

"Cristian S." <cs277_at_columbia.edu> wrote in message news:537e2d08.0107121359.1d18ebc1_at_posting.google.com...
> Hi,
> We just got a disk array with 12 x 9 GB drives where we want to move
> the database and I want to make sure we set it up right from the
> start. We have one oracle instance with one tablespace where all the
> action is.

Is it possible to split this. for example (assuming LMT) one tablespace for objects with (say) 128k extents and one for one with (say) 4M extents. Different disks.

>The disk array is only used by this application so space
> is not a concern (raid 0+1 or 1 are preffered to raid 5).
>
> Below is my proposed setup for the drives. Please let me know if
> something must be changed.
>
> Disks 1-4: RAID 0+1: datafiles, rollback segments, control files
>
> Disks 5-6: RAID 1: redo logs
>
> Disks 7-8: RAID 1: system and index tablespaces, archive logs, backups

total space avbailable on this disk is 1/2 the space available on disks 1-4. You *will* run out of space.
>
> Disks 9-10: RAID 1: application code for oracle
>
> Disk 11: No RAID: TEMP tablespace

what happens when this disk dies?
>
> Disk 12: Hot spare

where is the OS? Actually I am assuming the OS is on a different disk set somewhere.

I think I'd suggest

disks 1-4 (array A) user tablespace 1 (128K extents), index tablespace 2 (128k) RBS, system ts.
disks 5-8 (array B) user tablespace 1 (4m extents), index tablespace 2 (4m),redo logs,temp ts.
disks 9-12 (array C) archived redo logs,backups,control files.

I'd put the Oracle software on the same disk as the OS.

Bear in mind this is the result of maybe 15 minutes thinking top after i've been to the pub so it may not be entirely reasonable. <g>

The principles I've tried to follow tho are

  1. protect everything with at least mirroring.
  2. seperate frequently accessed tables and indices.
  3. seperate redo and archived logs.
--
Niall Litchfield
Oracle DBA
Audit Commission UK

Legal disclaimer required by my employer
****************************************************************************
**
This email contains information intended for the addressee only.
 It may be confidential and may be the subject of legal and/or professional
privilege.
Any dissemination, distribution, copyright or use of this communication
without prior permission of the addressee is strictly prohibited.
****************************************************************************
**
Received on Sat Jul 21 2001 - 16:35:54 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US