How to restore a database via RMAN but different DB_NAME?
I am trying to restore a database from RMAN but using a different DB_NAME/SID. The 'new' database is called DEV and I want to restore from an RMAN backup. Unfortunately, there is another db on the server called PROD, and the OLD PROD database is unavailable, hence the restore from rman backups.
I have managed to restore the controlfile from rman, but when I try to mount this database, so I can restore the datafiles, it says ORA-01103: database name 'PROD' in control file is not 'DEV'
Thanks. Rgds. Sheryl
Unfortunatly the 'old' prod (target) database is unavailable, therefore I can't use the duplicate database in rman.
And as the old prod is unavailable (server down), I can't use the 'tried and tested' method of 'Hot backups', copying the datafiles across and re-creating the controlfile. I have to use the RMAN backups from tape.
Hi, I am using the note 'Restore and Recover database on a new host', but I have come across another problem.
As I couldn't copy the rman backup files to the same directory structure as the orginal backup, the RESTORE DATABASE always errors with 'can not create datafile 1'. I assume this is because rman can't find the backuppiece sets, so I then catalog these backuppieces, but I still get the error. Thanks.
I have managed to sort this out. In the RMAN Documentation, its uses 'SET SCN 12345', but in a metalink note 419137.1, it uses 'SET SEQUENCE 12345'. I changed the SCN to SEQUENCE and now it is restoring the database. Very unusual...
One other option that you could also explore is, to install a new oracle home on the same server, edit the initialization file to set the db_name to PROD and restore the backup to a new location using the set new name command for each datafile.
Basically, RMAN expects that the db_name parameter matches with the name of the database in the control file. In one oracle home, you cannot have databases with same name..Hence, as a temporary workaround, you could setup a new oracle home, complete the recovery there, nid the database to rename it to DEV.
You could later get rid of this temporary oracle home and manage it from the original Oracle home.