Re: San & single point of failure

THey are probably correct, most SAN's work as you describe. the multiple control files are to guard against user error (ie, accidental deletes).

On Mon, Nov 17, 2008 at 2:50 PM, Claudia Zeiler <czeiler_at_ecwise.com> wrote:

> All,
>
> I have just been given a new server to put a database on. It is a SAN
> server, but the apparent layout of drives to me is:
>
> /redo1
>
> /redo2
>
> /big everything_else_disk
>
>
>
> This means that I have just put control_file1, 2, and 3 all in the same
> place – on /big. I thought that the whole point of multiple control files
> was to avoid single points of failure, such as a single location.
>
>
>
> I am told that SAN layout is to handle mirroring, striping, & hot spots
> behind the scene and I don't need to worry. If this is true, why do I need
> duplicates of the control file?
>
>
>
> Something smells fishy to me. Does anyone else have an opinion?
>
>
>
> -Claudia
>

-- 
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'

--
http://www.freelists.org/webpage/oracle-l