Database Reference
In-Depth Information
If the testing of the recovery succeeded, you'll see messages such as the following, indicating that the application
of redo was tested but not applied:
ORA-10574: Test recovery did not corrupt any data block
ORA-10573: Test recovery tested redo from change 4586939 to 4588462
ORA-10572: Test recovery canceled due to errors
ORA-10585: Test recovery can not apply redo that may modify control file
Here are some other examples of testing the recovery process:
RMAN> recover database test;
RMAN> recover tablespace users, tools test;
RMAN> recover datafile 1,2,3 test;
Restoring and Recovering the Entire Database
The RESTORE DATABASE command will restore every data file in your database. The exception to this is when RMAN
detects that data files have already been restored; in that case, it will not restore them again. If you want to override
that behavior, use the FORCE command.
When you issue the RECOVER DATABASE command, RMAN will automatically apply redo to any data files that need
recovery. The recovery process includes applying changes found in the following files:
Incremental backup pieces (applicable only if using incremental backups)
Archived redo log files (generated since the last backup or incremental backup applied)
Online redo log files (current and unarchived)
You can open your database after the restore-and-recovery process is complete. Complete database recovery
works only if you have good backups of your database and access to all redo generated after the backup was taken.
You need all the redo required to recover the database data files. If you don't have all the required redo, then you'll
most likely have to perform an incomplete recovery (see the section “Incomplete Recovery,” later in this chapter).
your database has to be at least mounted to restore data files, using rMaN. this is because rMaN reads
information from the control file during the restore-and-recovery process.
Note
You can perform a complete database-level recovery with either the current control file or a backup control file.
Using the Current Control File
You must first put your database in mount mode to perform a database-wide restore and recovery. This is because
Oracle won't allow you to operate your database in open mode while data files associated with the SYSTEM tablespace
are being restored and recovered. In this situation, start up the database in mount mode, issue the RESTORE and
RECOVER commands, and then open the database, like so:
$ rman target /
RMAN> startup mount;
RMAN> restore database;
RMAN> recover database;
RMAN> alter database open;
 
 
Search WWH ::




Custom Search