San & single point of failure

From: Claudia Zeiler <>
Date: Mon, 17 Nov 2008 12:50:45 -0800
Message-ID: <B47109E95A4F8C4AB42CC4D4169D997B1463B77F81@ecsrm01.ecwise.local>

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:
/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?


Received on Mon Nov 17 2008 - 14:50:45 CST

Original text of this message