--------------------
When attempting to restore database the error stack follows.
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
<.......>
RMAN-06023: no backup or copy of datafile 1 found to restore
Solution Description
--------------------
Some common reasons why a file can not be restored are that,
1)There is no backup or copy of the file that is known to recovery manager, or there are no backups or copies that fall within the criteria specified on the RESTORE command, or
2)Some datafile copies have been made but not cataloged.
Scenario 1:
-------------
You have added a new tablespace since your last backup.Now you issued just RESTORE DATABASE command without "SET UNTIL" clause. The restore job fails because it is looking for a backup of the datafile that belongs to the the new tablespace that has been added since the last backup was taken.
Solution Description:
You need to specify the "SET UNTIL" time clause in the restore job to a time
before the new tablespace was added.
Explanation:
When a restore command is run from RMAN and if no "SET UNTIL" clause is defined, RMAN will try and restore backups for all the datafiles in the database at the present time. If a "SET UNTIL" clause is defined, then RMAN will restore only the datafiles that exist in the database that match the specified point of time in the "SET UNTIL" time clause.
Scenario 2:
--------------
You are attempting to restore a database using Oracle Recovery Manager (RMAN) using a 'set time' parameter to do a point-in-time recovery and the error stack came as above. Whenever you invoke 'list backupset of database' command shows there to be multiple backups of these files available.
Solution Description:
You have issued a 'resetlogs' prior to the last backup but before the 'Until Time' clause in the RMAN script. For instance, the last backup of the database was June 8, 2008.On June 9, you opened the database with resetlogs. Then, you decide to restore the database to a point in time on June 10. Because you cannot roll forward through the resetlogs, RMAN cannot find any legitimate backups to restore from within this incarnation.
The solution is to set the 'until time' clause to a time before the resetlogs.
Explanation:
You need to check the incarnation of the database:
rman>list incarnation of database;
If the current incarnation reset time falls between the last backup and the time specified for 'Set Time,' then the recovery catalog acknowledges that there are no backups that match the time criteria specified, and errors out with RMAN-6023.
Related Documents
No comments:
Post a Comment