As discussed in Choosing the location for the RMAN repository, for an RMAN backup strategy you must first choose a location for the RMAN repository. By default, this repository is maintained in the Control File. However, for larger or more mission-critical databases, create a Recovery Catalog database that can store a much longer history than the Control File.
Next, allocate space to be used by the catalog schema. The size of the Recovery Catalog schema depends on the number of databases managed by the catalog. The schema also grows as the number of archived redo log files and backups for each database increases. For more information on sizing the Recovery Catalog schema, see Planning the Size of the Recovery Catalog Schema in the Oracle Database Backup and Recovery Advanced User’s Guide.
1 |
Start SQL*Plus, and connect with administrator privileges to the database that will contain the Recovery Catalog. |
3 |
Grant the RECOVERY_CATALOG_OWNER role to the schema owner. |
4 |
After creating the catalog owner, create the catalog tables with the RMAN CREATE CATALOG command. This command creates the catalog in the default tablespace of the catalog owner.
2 |
Run the CREATE CATALOG command to create the catalog. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center