D RMAN Compatibility

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

See Also:

Oracle Database Upgrade Guide

D.1 About RMAN Compatibility

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

Table D-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

Starting with Oracle Database 12c, the version of the RMAN client, target database, and auxiliary database must be the same. The recovery catalog schema can be any supported catalog schema whose version is greater than the version of the RMAN client. For example an Oracle Database 12c RMAN client can only connect to a target database whose version is Oracle Database 12c, an auxiliary database whose version is Oracle Database 12c, and a recovery catalog schema that is created in an Oracle Database 12c or higher version.

D.2 Determining the Recovery Catalog Schema Version

Use a SQL query to determine the version of the recovery catalog schema.

To determine the current release of the recovery catalog schema:

  1. Use SQL*Plus to connect to the recovery catalog database as the catalog owner. For example, enter: 
    % sqlplus rco@catdb
  2. Query the rcver catalog table. For example, run this query: 
    SQL> SELECT * FROM rcver; 

     VERSION 
     ------------ 
     12.01.00.01

D.3 RMAN Compatibility Matrix

There are certain rules for RMAN compatibility.

Rules for RMAN compatibility include:

  • The version of the RMAN client must be equal to the version of the target database.

  • The version of the auxiliary database must be equal to the version of the RMAN client.

  • The version of the recovery catalog schema must be greater than or equal to the version of the RMAN client.

  • Any release of Oracle Database can restore backup sets and copies created by any prior Oracle Database release.

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

Table D-2 RMAN Compatibility Table

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

>= 12.1.0.x

= target database executable

>= 12.1

(with COMPATIBLE parameter >=12.1)

>= RMAN client version
18.x = target database executable

>= 12.1

(with COMPATIBLE parameter >=12.1)

>= RMAN client version
19.x = target database executable

>= 12.1

(with COMPATIBLE parameter >=12.1)

>= RMAN client version
20.x = target database executable

>= 12.1

(with COMPATIBLE parameter >=12.1)

>= RMAN client version
21.x = target database executable

>= 12.1

(with COMPATIBLE parameter >=12.1)

>= RMAN client version
23ai = target database executable

>= 12.1

(with COMPATIBLE parameter >=12.1)

>=RMAN client version

When using an older version of the RMAN client with a newer version of the database, you do not get the features added in the newer version.

D.4 RMAN Compatibility: Scenario

This section contains an example of the RMAN client versions and recovery catalog database versions used for production databases that use various Oracle Database versions.

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

  • Oracle Database 12c Release 1(12.1)

  • Oracle Database release 18c

  • Oracle Database release 19c

  • Oracle Database release 21c

  • Oracle Database release 23ai

Use the highest production database version as the recovery catalog schema version to store the metadata for all the production databases.