Database Reference
In-Depth Information
■
you can also use the
NID
utility to change the database name and database identifier (dBId). see Mos
note 863800.1 for more details.
Tip
Summary
RMAN is an acronym for Recovery Manager. It's worth noting that Oracle did not name this tool Backup Manager.
The Oracle team recognized that although backups are important, the real value of a B&R tool is its ability to restore
and recover the database. Being able to manage the recovery process is the critical skill. When a database is damaged
and needs to be restored, everybody looks to the DBA to perform a smooth and speedy recovery of the database.
Oracle DBAs should use RMAN to protect, secure, and ensure the availability of the company's data assets.
The restore-and-recovery process is analogous to the healing process involved when you break a bone. Restoring
data files from a backup and placing them in their original directories can be likened to setting a bone back to its
original position. Recovering a data file is similar to the healing of a broken bone—returning the bone back to the state
it was in before it was broken. When you recover data files, you apply transactions (obtained from archive redo and
online redo) to transform the restored data files back to the state they were in before the media failure occurred.
RMAN can be used for any type of restore-and-recovery scenario. Depending on the situation, RMAN can be
used to restore the entire database, specific data files, control files, server parameter files, archive redo logs, or just
specific data blocks. You can instruct RMAN to perform a complete or an incomplete recovery.
The last section in this chapter details how to use RMAN to restore and recover a database to a remote server.
I recommend that you periodically attempt this type of recovery in order to exercise your B&R strategy. You will gain
much confidence and fully understand B&R internals once you can successfully restore a database to a server that is
different from the original.
