Re: Redo + Archive + Data Layout...

Sounds good ...

A few pointers:

Don't mirror the REDOs at the OS level - use single disks and at least two members per group, on different disks. OS mirror your archive dest. If you've got two extra disks to spare and your system is write heavy -- the redo switches should alternate back and forth between two drives so that archiver and redo don't hit the same drive at the same time.

No need to mirror any tablespace by itself on just RAID 1 -- you can use RAID 5 or 1+0.

Put your controlfile copies on the same disks as your REDO. Recovery is a snap when you have the current control file. Set your stripe size to 128k for the tablespaces.

Domenic.

hari_om_at_hotmail.com (Hari Om) wrote in message news:<d1d5ebe4.0310200550.549e0a57_at_posting.google.com>...
> I am using Oracle 9.2.0.1 on IBM AIX 5.1L
> I have come along with the following disk layout for my Database...can
> anyone point out if there would be any issues:
>
> hdisk0(18GB) + hdisk1 (18GB) --> These are MIRRORED. It contains OS +
> Oracle SW + Control file copy 1
>
> hdisk2(36GB) + hdisk3 (36GB) --> These are MULTIPLEXED by Oracle. It
> contains Redo Logs.
>
> hdisk4(36GB) + hdisk5 (36GB) --> These are MULTIPLEXED by Oracle. It
> contains Archive Destination.
>
> hdisk6(36GB) + hdisk7 (36GB) --> These are MIRRORED. It contains
> SYSTEM Tablespace.
>
> hdisk8 + hdisk9 + hdisk10 + hdisk11 + hdisk12 + hdisk13 --> Each are
> 72 GB. These are MIRRORED and STRIPPED (1+0)--> These contain Oracle
> DATA fiels + Control File copy
>
> Can anyone point out any issues in the above layout....?
> Would it fine if we don't MIRROR REdo Logs?
>
> THANKS!
Received on Mon Oct 20 2003 - 14:42:52 CDT