This content has been marked as final. Show 6 replies
RMAN-07518: Reason: Foreign database file DBID: string Database Name: string
Cause: This is an informational message only.
Action: No action is required.
You cannot use backup of one database for the recovery of another database and also cannot catalog the backups of another database. Because there is a difference in DBID in both database. You can instead use transportable tablesapce feature to have the data of particular tablespace from one database to another.
on 10g R2 ,I try to use the RMAN backup files from another data base for my database :Your work is wrong.Firstly why you want using another database backups for other database?,second this will not work even these have same DBID.So choose correct ways and steps perform your backup and recovery operations.
on 10g R2 ,I try to use the RMAN backup files from another data base for my database :You mean you are trying to use RMAN backup and create new db wiht that backup or you mean try to use one database backup to recover one other db.
For option 1 its possible, for option 2 its not
I was trying to find a way to use the RMAN backups to create a new DB supposing that the original target has completely deleted. I have always appreciated HOT Backups since they are useable to create a database in any circumstance (by creating control file).
Up to you then RMAN Backup files are unusable if target database is deleted.
Helios, how can I use them to create a new DB ? (Option 1)
Unfortunately, what you have said is entirely wrong. The restoration of a database to a second server is something that alot of people/organisations do. The reason is because of disaster recovery.
If I use DUPLICATE DATABASE to restore to a test server, I end up with a different DBID for each restoration which is not always desireable (for example if the server is a part of a Data Guard configuration). Of course, I could use Data Pump but that is a lot of unecessary work and it takes a good while longer when dealing with databases in the Terabyte range.
The correct answer to the question is the following:
From the RMAN prompt:
SET DBID= 12345678;
RESTORE SPFILE TO '<path>' from '<path>';
RESTORE CONTROLFILE FROM AUTOBACKUP;
There is of course a good deal more to add to the list but that is the basis for the restoration.