Renaming inconsistent database

Hi,

In a testing scenario, the following question arose:

• Production database PROD_DB runs on machine A (in ARCHIVELOG mode)
• Machine A crashes, leaving PROD_DB inconsistent
• When restarting machine A, the database is set to *not* automatically start
• A copy of *all* files of PROD_DB is written to tape. (Including controlfiles, online redologs, etc.)
• On machine A, the PROD_DB is restarted. After automatic media recovery, PROD_DB works fine.
• The copy from tape is written to machine B. The intention is to rename the copied database on machine B to COPY_DB.

On machine B, there is now a copy of PROD_DB in an inconsistent state. Is it safe to do:

STARTUP NOMOUNT
CREATE CONTROLFILE REUSE SET DATABASE "COPY_DB" RESETLOGS NOARCHIVELOG         <other parameters>;

... at this point, or is it necessary to make the copy consistent first?

Thanks,

-- 
Jurjen Oskam

PGP Key available at http://www.stupendous.org/