Databases Reference
In-Depth Information
Solution
Table 17-2 lists Oracle's RMAN compatibility matrix. The easiest way to use this matrix is to find the version of your
database in the “Target/Auxiliary DB” column and then use that row for determining the compatibility required for
other RMAN components in your environment.
Table 17-2. RMAN Compatibility Matrix
Target/Auxiliary DB
RMAN Executable
Catalog DB
Catalog Schema
8.1.7.4
8.1.7.4
>=8.1.7
8.1.7.4 or >=9.0.14
9.0.1
9.0.1
>=8.1.7
>= RMAN executable
9.2.0
>= 9.0.1.3 and <= target database
>=8.1.7
>= RMAN executable
10.1.0
>= 9.0.1.3 and <= target database
>=9.0.1
>= RMAN executable
10.2.0
>= 9.0.1.3 and <= target database
>=9.0.1
>= RMAN executable
11.1.0
>= 9.0.1.3 and <= target database
10.2.0.3
>= RMAN executable
11.2.0
>= 9.0.1.3 and <= target database
10.2.0.3
>= RMAN executable
12.1.0
TBD
TDB
TBD
Tip
You can also find the rMan compatibility matrix information in Mos note 73431.1.
How It Works
Ideally, you'd like all your environments to be at the same Oracle version. In reality, that rarely is the case. Therefore,
in most environments, you will have to deal with some RMAN compatibility issues. Here are the general rules of
thumb when dealing with RMAN compatibility problems:
rman executable should be the same as your
Whenever possible, the version of the
target/auxiliary database version.
rman executable.
The version of the catalog schema must be at the same version or newer than the
The version of the catalog database is backward compatible with earlier versions of the target
database.
If you're not sure which version of the catalog schema you are using, connect via SQL*Plus to the recovery catalog
as the catalog owner and run this query:
SQL> select * from rcver;
Dealing with an ORA-19511 Error
Problem
You're receiving an ORA-19511 error message from your media management layer (MML).
 
 
Search WWH ::




Custom Search