Databases Reference
In-Depth Information
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:
•
Incremental backup pieces (applicable only if using incremental backups)
•
Archived redo log files (generated since the last backup or last incremental backup that
is 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 have 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, you'll
most likely have to perform an incomplete recovery. See Chapter 12 for details on performing an incomplete recovery.
Performing Tablespace-Level Recovery
Problem
You're seeing a media error associated with several data files contained in one tablespace. You want to perform
complete recovery on all data files associated with that problem tablespace.
Solution
Use the
restore tablespace
and
recover tablespace
commands to restore and recover all the data files associated
with a tablespace. You can either place the database in mount mode or have the database open (if it's not the system
or undo tablespace). In the first scenario, we'll place the database in mount mode for the restore and recovery.
Recover While Database Not Open
This solution works for any tablespace in your database. In this example, we restore the users tablespace:
$ rman target /
RMAN> startup mount;
RMAN> restore tablespace users;
RMAN> recover tablespace users;
RMAN> alter database open;
If everything was successful, the last message you should see is this:
Statement processed
Keep in mind that if you're using a recovery catalog, you should connect to it when performing restore and
recover operations, for example:
$ rman target / catalog rcat/rcat@rcat
