Purpose of Recover Command:
----------------------------------------
1)Performing complete recovery of one or more restored datafiles or entire database.
2)Performing incomplete recovery of a database (DBPITR) or tablespace (TSPITR).
3)Applying incremental backups to a datafile image copy (not a restored datafile) to roll it forward in time.
Restriction of Recover Command:
-------------------------------------
•You cannot arbitrarily recover individual datafiles to different points in time. You can recover the whole database to a single point in time (DBPITR, in which case you should use SET UNTIL, followed by RESTORE DATABASE and RECOVER DATABASE) or recover wholly contained tablespaces to a point in time different from the rest of the database (TSPITR, in which case you must use RECOVER TABLESPACE... UNTIL...).
•For whole database recovery database must be in mounted stage but not open. For individual datafile or individual tablespace recovery database must be either mounted or open. If database is open state then the intended datafile or tablespace must be in offline state.
•The RECOVER DATABASE command does not recover any files that are offline normal or read-only at the point in time to which the files are being recovered. However if CHECK READONLY is specified, then RMAN checks each read-only file on disk to ensure that it is already current at the desired point in time.
•You must open the database with the RESETLOGS option after incomplete recovery or recovery with a backup control file.
•RMAN can recover through RESETLOGS operations transparently if the datafiles to be recovered are from a parent incarnation. If required, the RECOVER command can also restore and apply archived logs and incremental backups from prior incarnations.
•If, during recovery of a tablespace or database, the database encounters redo for adding a datafile, RMAN automatically creates a new datafile.
•You cannot manually allocate channels and then run RECOVER with the DEVICE TYPE option.
No comments:
Post a Comment