An Oracle RMAN (Recovery Manager) recovery catalog is a critical mechanism for managing database backup information. In this article, we will explain in detail the practical procedures for importing (IMPORT CATALOG), upgrading (UPGRADE CATALOG), and dropping (DROP CATALOG) a recovery catalog.
1. Importing a Recovery Catalog
The IMPORT CATALOG command is used when merging different recovery catalogs. This allows you to integrate information from an existing recovery catalog into a new one.
Prerequisites for Import
- A new recovery catalog schema must be created, and the recovery catalog must be registered.
- You must have access to the source recovery catalog.
- Verify the consistency between the source and target catalogs.
Import Procedure
- Start RMAN and connect to the new recovery catalog.
RMAN> CONNECT CATALOG new_user/new_password@new_catalog_db;
- Use the
IMPORT CATALOGcommand to import data from the old catalog.
RMAN> IMPORT CATALOG old_user/old_password@old_catalog_db;
- Once the import is complete, verify the contents of the integrated recovery catalog.
RMAN> LIST BACKUP;
- As necessary, check if redundant information has been integrated and organize it.
2. Upgrading a Recovery Catalog
When you upgrade to a new version of Oracle Database, you must update the structure of the recovery catalog.
Prerequisites for Upgrade
- The RMAN catalog must be operating normally.
- You must be able to connect using the RMAN executable of the new Oracle version.
- Check the
RCVERtable to understand the existing version.
Upgrade Procedure
- Start RMAN and connect to the recovery catalog.
RMAN> CONNECT CATALOG catalog_user/catalog_password@catalog_db;
- Execute the
UPGRADE CATALOGcommand to upgrade the catalog.
RMAN> UPGRADE CATALOG;
- To confirm the upgrade is complete, connect to the recovery catalog via SQL*Plus and check the version.
sqlplus catalog_user/catalog_password@catalog_db
SQL> SELECT * FROM RCVER;
- After confirming the upgrade has been applied, take a backup of the catalog.
[oracle@restart ~]$ $ORACLE_HOME/OPatch/opatch lspatches
35643107;Database Release Update : 19.21.0.0.231017 (35643107) ★19.21
29585399;OCW RELEASE UPDATE 19.3.0.0.0 (29585399)
OPatch succeeded.
[oracle@restart ~]$ sqlplus rcuser/oracle@rcatalog
SQL*Plus: Release 19.0.0.0.0 - Production on Sun Feb 16 12:51:10 2025
Version 19.21.0.0.0
Copyright (c) 1982, 2022, Oracle. All rights reserved.
Last Successful login time: Sun Feb 16 2025 12:24:11 +09:00
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.21.0.0.0
SQL> select * from rcver;
VERSION
---------------------------------------------
19.03.00.00.00 ★19.3
SQL> exit
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.21.0.0.0
[oracle@restart ~]$ rman target / catalog rcuser/oracle@rcatalog
Recovery Manager: Release 19.0.0.0.0 - Production on Sun Feb 16 12:51:46 2025
Version 19.21.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 19.03.00.00 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 19.03.00.00 in TARGET database is not current
connected to target database: V19 (DBID=2960846808)
connected to recovery catalog database
PL/SQL package RCUSER.DBMS_RCVCAT version 19.03.00.00. in RCVCAT database is not current
PL/SQL package RCUSER.DBMS_RCVMAN version 19.03.00.00 in RCVCAT database is not current
RMAN> upgrade catalog; ★Upgrade
recovery catalog owner is RCUSER
enter UPGRADE CATALOG command again to confirm catalog upgrade
RMAN> upgrade catalog;
recovery catalog upgraded to version 19.21.00.00.00
DBMS_RCVMAN package upgraded to version 19.21.00.00
DBMS_RCVCAT package upgraded to version 19.21.00.00.
RMAN> exit
Recovery Manager complete.
[oracle@restart ~]$ sqlplus rcuser/oracle@rcatalog
SQL*Plus: Release 19.0.0.0.0 - Production on Sun Feb 16 12:53:18 2025
Version 19.21.0.0.0
Copyright (c) 1982, 2022, Oracle. All rights reserved.
Last Successful login time: Sun Feb 16 2025 12:51:48 +09:00
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.21.0.0.0
SQL> select * from rcver;
VERSION
---------------------------------------------
19.21.00.00.00 ★19.21
3. Dropping a Recovery Catalog
If a recovery catalog is no longer needed, it can be deleted using the DROP CATALOG command.
Prerequisites for Dropping
- Ensure that you have backed up the RMAN catalog data.
- Confirm that the recovery catalog is indeed unnecessary.
- Verify that the target databases registered in the catalog are functioning correctly.
Dropping Procedure
- Start RMAN and connect to the recovery catalog.
RMAN> CONNECT CATALOG catalog_user/catalog_password@catalog_db;
- Execute the
DROP CATALOGcommand.
RMAN> DROP CATALOG;
- Once the deletion is complete, verify that the catalog no longer exists.
RMAN> LIST INCARNATION;
- As necessary, check the impact after deletion and review backup and restore settings.
Summary
| Operation | Command |
| Import Recovery Catalog | IMPORT CATALOG old_user/old_password@old_catalog_db; |
| Upgrade Recovery Catalog | UPGRADE CATALOG; |
| Drop Recovery Catalog | DROP CATALOG; |
Proper management of the recovery catalog is essential to ensure reliable database backup and recovery. Make sure to thoroughly understand the procedures for importing, upgrading, and dropping to maintain appropriate operations.
Target Version: 19c
[reference]
Recovery Catalog Views
コメント