Skip Headers
Oracle® Database Backup and Recovery Reference
11g Release 1 (11.1)

Part Number B28273-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

B RMAN Compatibility

This appendix describes the requirements for compatibility among the different components of the Recovery Manager (RMAN) environment. This appendix contains these topics:

About RMAN Compatibility

Table B-1 describes the components of an RMAN environment. Each component has a release number associated with it.

Table B-1 Components of an RMAN Environment

Component Release Number Refers to ...

RMAN client

Version of RMAN client (displayed when you start RMAN)

Recovery catalog database

Version of Oracle Database

Recovery catalog schema in recovery catalog database

Version of RMAN client used to create the recovery catalog

Target database

Version of Oracle Database

Auxiliary database

Version of Oracle Database


For example, you can use a release 9.0.1 RMAN client with:

Determining the Recovery Catalog Schema Version

To determine the current release of the catalog schema, you must run a SQL query.

  1. Use SQL*Plus to connect to the recovery catalog database as the catalog owner. For example, enter:

    % sqlplus rman/rman@catdb
    
  2. Query the rcver catalog table. For example, run this query:

    SQL> SELECT * FROM rcver; 
    
         VERSION 
         ------------ 
         09.00.01.00
         10.02.01.00
         11.01.00.03
    

    If multiple versions are listed, then the last row is the current version, and the rows before it are prior versions. In the preceding example, the current recovery catalog schema version is 11.1 and the previous version was 10.2.

    Note that for releases 10.2 and later, the last two digits in the rcver output indicate patch level. For earlier releases, they are always zeros.

RMAN Compatibility Matrix

In general, the rules of RMAN compatibility are as follows:

Table B-2 shows version requirements for RMAN components. Note that the symbol >= before a release means all Oracle Database releases from this release or later along with their patches.

Table B-2 RMAN Compatibility Table

Target/Auxiliary Database RMAN client Recovery Catalog Database Recovery Catalog Schema

8.0.6

8.0.6

>=8.1.7

>=8.0.6

8.1.7

8.0.6.1

>=8.1.7

>=8.1.7

8.1.7

8.1.7

>=8.1.7

>=RMAN client

8.1.7.4

8.1.7.4

>=8.1.7

8.1.7.4

8.1.7.4

8.1.7.4

>=8.1.7

>= 9.0.1.4

9.0.1

9.0.1

>=8.1.7

>= RMAN client

9.2.0

>=9.0.1.3 and <= target database executable

>=8.1.7

>= RMAN client

>=10.1.0

>=9.0.1.3 and <= target database executable

>=9.0.1

>= RMAN client


When using an older version of the RMAN client with a newer version of the database, you do not get the features of the newer version. For example, when using the Oracle9i RMAN client to back up an Oracle Release 10g database, you will not have access to features like the flash recovery area, flashback database, TSPITR with an RMAN-managed auxiliary instance, or recovery through RESETLOGS.

Cross-Version Compatibility of Recovery Catalog Exports and Imports

Data Pump Exports of the recovery catalog are often used as a way to backup its contents. When planning to use Data Pump Export to make a logical backup of the recovery catalog, see Oracle Database Utilities for details on compatibility issues relating to the use of database exports across versions of Oracle Database.

Exports from a later version of the database cannot be imported into databases running under earlier versions. You must export your recovery catalog data using the export utility from the earliest version of Oracle Database that you need to use for a recovery catalog.

For example, if you want to export recovery catalog data from a 9.2.0.5 database and you expect to import it into an 8.1.7.4 version of Oracle for disaster recovery, you must use the export utility from the 8.1.7.4 release of Oracle to perform the export operation. Otherwise, the import operation will fail.

RMAN Compatibility: Scenario

Assume that you maintain a production databases of the following releases:

You want to record RMAN repository data about these databases in a single recovery catalog database. According to Table B-2, you can use a single 11.1.0 recovery catalog database with a 11.1.0 catalog schema for all target databases. Ensure that the version of the RMAN client used to back up each target database meets the following requirements: