Create an RMAN recovery catalog and register the database
OracleRMANCommand
-- 1) In the catalog database (separate DB/PDB), with sqlplus:
CREATE TABLESPACE rcat_ts DATAFILE '/u02/oradata/RCAT/rcat01.dbf' SIZE 1G AUTOEXTEND ON NEXT 256M;
CREATE USER rcat IDENTIFIED BY "<password>"
DEFAULT TABLESPACE rcat_ts QUOTA UNLIMITED ON rcat_ts;
GRANT RECOVERY_CATALOG_OWNER TO rcat;
# 2) From the shell: create the catalog schema
rman catalog rcat@<rcat_tns>
CREATE CATALOG;
# 3) Register the target database and verify:
rman target / catalog rcat@<rcat_tns>
REGISTER DATABASE;
REPORT SCHEMA;
# Resync controlfile records into the catalog (done automatically after backups):
RESYNC CATALOG;What it does
Builds a recovery catalog that stores backup metadata in a central schema, independent of the controlfile retention (control_file_record_keep_time), and registers the target database.
When to use it
To keep the backup history of many databases in one place, to use primary/standby backups interchangeably in Data Guard, and for long-term (KEEP) backups and stored scripts.
Caution
The catalog database must be on a different server from the databases it protects and must itself be backed up. The catalog schema version cannot be lower than the newest RMAN client in use; a newer client requires UPGRADE CATALOG. In Data Guard register only the primary; standbys are defined by DB_UNIQUE_NAME with CONFIGURE DB_UNIQUE_NAME ... CONNECT IDENTIFIER.
Related
- Create a physical standby from the active database with RMAN DUPLICATE
- Validate and clean up RMAN backup records (CROSSCHECK, EXPIRED, OBSOLETE)
- Validate the database and backups against corruption (VALIDATE)
- See which backups a restore would use and validate them (PREVIEW / VALIDATE)
- Repair corrupt blocks online (block media recovery, RECOVER CORRUPTION LIST)
- Return a tablespace to a point in the past (TSPITR)