Skip Headers

Oracle® Database Recovery Manager Reference
10g Release 1 (10.1)

Part Number B10770-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
Feedback

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

B
RMAN Compatibility

This section contains these topics:

About RMAN Compatibility

The following table describes the components of an RMAN environment. Each component has a release number associated with it.

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:

Determination of 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 
         ------------ 
         08.01.05
         09.00.01
    
    

    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 catalog schema version is 09.00.01 and the previous version was 08.01.05.

RMAN Compatibility Matrix

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

Table B-1 shows version requirements for RMAN components. Note the following conventions when interpreting this table:

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.

Table B-1 RMAN Compatibility Table
Target/Auxiliary Database RMAN client Catalog Database 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

>=8.1.7

>= RMAN client

10.1.0

>=9.0.1.3

>=9.0.1

>= RMAN client

RMAN Compatibility: Scenario

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

You want to record metadata about these databases in a single recovery catalog database. According to Table B-1, you can use a single 9.2.0 recovery catalog database with a 10.1.0 catalog schema for all target databases.

The solution for this combination of target databases is to do the following: