We have an Oracle database running in a SAN with Data Files, Control files, etc., all contained on SAN-based logical luns. In the event of a server crash, the DR plan is to present the SAN LUNS which comprises the Oracle database on source machine to another similarly sized machine at another target site. (The source SAN LUNS are mirrored to this target site). The plan then is to bring the crashed source database up as a differently named database from the original source DB name (but same name as existing database on target machine), and then once opened successfully, to continue pre-crash application activities on the target machine using the newly presented database. Does this plan sound feasible? Will the crashed DB be able to be brought up and recovered under a different DB name on the target machine?
All of the above is feasible and is done for various disaster recovery plans. The only thing I would change is where you rename the DB name. Why go through this step? When your source server becomes available, you would have to change the DB name back to its original name. And I'm not sure what you gain by changing the DB name here. Otherwise, if you also have your archived redo logs on the same SAN, you should be able to mount the database and apply recovery and get up and running.
Dig Deeper on Oracle database administration
Oracle expert Brian Peasland answers one reader's question about common pitfalls when connecting Oracle to outside programs.
One reader asks expert Brian Peasland a question about datafile sizes with the Oracle RMAN duplicate 10g command.
Managing parent table-child table relations in Oracle SQL environments is key to efficient programming.
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.