Were they possibly referring to things like missing registry entries or incompatible (or missing) Oracle binaries, such as older versions and the like? Even on Unix you would need to make sure that the "oracle" user and "dba" groups existed and that path setups were correct. It helps if the uids and gids match so if your database files are on file systems you don't have to chown them. Also likely some things not on the disk set for the database per se like tnsnames.ora and listener.ora might need updates. All that said, this is a pretty normal thing to do, and it is not rocket science to prepare a server to accept a new database entirely contained on freshly mounted disks. This has pretty much worked since at least Oracle V5. If I recall correctly the host name was part of the password encryption prior to V5 and that caused problems. mwf -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Mike Schmitt Sent: Thursday, October 13, 2005 3:34 PM To: oracle-l@xxxxxxxxxxxxx Subject: Disk failover Hi All, Can someone please confirm for me the ability to unmount a set of disks on Server A, mount those same disks onto Server B (Same O/S, unique named disks), and bring up the database on server B. I know I have done this before, but I was just in a meeting where someone told me that you can't do this with Oracle, and that they tested it. This is with 9i by the way Thanks -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l