upgrade oracle rman catalog

wisdomone1發表於2009-12-02

Upgrading the Recovery Catalog

If you use a version of the recovery catalog that is older than that required by the RMAN client, then you must upgrade it. For example, you must upgrade the catalog if you use a release 8.1 version of the RMAN client with a release 8.0 version of the recovery catalog.

You receive an error when issuing UPGRADE CATALOG if the recovery catalog is already at a version greater than that required by the RMAN client. RMAN permits the UPGRADE CATALOG command to be run if the recovery catalog is current and does not require upgrading, however, so that you can re-create packages at any time if necessary. Check the message log for error messages generated during the upgrade.

To upgrade the recovery catalog:

  1. To install the new recovery catalog schema, the recovery catalog user must have TYPE privilege:

    sqlplus> connect sys/oracle@catdb as sysdba;
    sqlplus> grant TYPE to rman;

    Use RMAN to connect to the target and recovery catalog databases. For example, enter:

    % rman TARGET / CATALOG rman/cat@catdb

    connected to recovery catalog database
    PL/SQL package rcat.DBMS_RCVCAT version 08.00.04 in RCVCAT database
    is too old

    Issue the UPGRADE CATALOG command:

    UPGRADE CATALOG;

    recovery catalog owner is rman
    enter UPGRADE CATALOG command again to confirm catalog upgrade

    Enter the UPDATE CATALOG command again to confirm:

    UPGRADE CATALOG;

    recovery catalog upgraded to version 09.02.00
    DBMS_RCVMAN package upgraded to version 09.02.00
    DBMS_RCVCAT package upgraded to version 09.02.00

    See Also:

    • for UPGRADE CATALOG command syntax

Dropping the Recovery Catalog

If you do not want to maintain a recovery catalog, then you can drop the recovery catalog schema from the tablespace. The DROP CATALOG command deletes all information from the recovery catalog. Hence, if you have no backups of the recovery catalog schema, then backups of all target databases managed by this catalog may become unusable. (The control file of the target database will still retain a record of recent backups.)

The DROP CATALOG command is not appropriate for unregistering a single database from a recovery catalog that has multiple target databases registered. Dropping the catalog deletes the recovery catalog record of backups for all target databases registered in the catalog.

To drop the recovery catalog schema:

Use RMAN to connect to the target and recovery catalog databases.

% rman TARGET / CATALOG rman/cat@catdb

Issue the DROP CATALOG command twice to confirm:

DROP CATALOG;

recovery catalog owner is rman
enter DROP CATALOG command again to confirm catalog removal

DROP CATALOG;

來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/9240380/viewspace-621211/,如需轉載,請註明出處,否則將追究法律責任。

相關文章