Recovery Catalog Database
The recovery catalog database is an optional repository used by RMAN to record information concerning backup and recovery activities performed on the target. The recovery catalog consists of three components:
A separate database referred to as the catalog database (from the target database)
A schema within the catalog database
Tables (and supporting objects) within the schema that contain data pertaining to RMAN backup and recovery operations performed on the target
The catalog is typically a database that you build on a different host from your target database. The reason for this is that you don’t want a failure on the target host to affect your ability to use the catalog. If both the catalog and target are on the same box, a single media failure can put you in a situation from which you can’t recover your target database.
Inside the catalog database is a special schema containing the tables that store information about RMAN backup and recovery activities. This includes information such as:
Details about the physical structure of the target database
A log of backup operations performed on the target database’s datafiles, control files, and archived redo log files
Stored scripts containing frequently used sequences of RMAN commands
Why is the catalog optional? When RMAN performs any backup operation, it writes information about that task to the target database’s control files. Therefore, RMAN does not need a catalog to operate. If you choose to implement ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access