One "Lesson Learned" here is to keep at least one copy of the control files
off of the SAN.  OK, so ours is currently just an icky AutoRAID subsystem,
but it has a separate power cord which can be accidentally kicked out of the
locking socket, even when you're working on a completely different set of
systems.

Rich

Rich Jesse                           System/Database Administrator
[EMAIL PROTECTED]                  Quad/Tech Inc, Sussex, WI USA


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 22, 2003 1:05 PM
> To: Multiple recipients of list ORACLE-L
> Subject: OFA and Shared Storage
> 
> 
> I read some posts on here with shared storage such as SAN and 
> Network Appliances its no longer necessary to multiplex 
> datafiles on different disks, since the storage array handles 
> that for you. 
> 
> How do you ensure that control files and redo log files are 
> kept safely apart so that no one disk failure in the shared 
> storage can take them all out?
> 
> According to the OFA(well the abbreviated version I have in 
> front of me) 4-5 disks is optimal for multiplexing. Does this 
> no longer apply with shared storage? How do you ensure 
> database available with shared storage? if your not 
> multiplexing datafiles? 
> 
> I may have read some peoples posts incorrectly. Im just 
> digging into backup and recovery. 
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Jesse, Rich
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to