RMAN-06429: TARGET database is not compatible with this version of RMAN

Whenever you connect to a database (rman version if different from source database version in fact rman version is higher than the source database) through RMAN using/without recovery catalog it fails with RMAN-06429: TARGET database is not compatible with this version of RMAN as below.

C:\>rman target rman/rman@local2 catalog rman/rman@testdb

Recovery Manager: Release 10.2.0.1.0 - Production on Tue Mar 24 05:07:14 2009

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.1.0.0 req
uired
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN

Cause of the Problem
You have higher RMAN version than the target database (to which you are connecting). In order to successfully connect to database by rman the rman version must be less or equal to the target database version.

Solution of the Problem
There is a rule of thumb in this connecting issue and it is best practice to use 'rule of thumb'. That is "always use the target database RMAN executable and the latest release of Oracle for your recovery catalog."

However, if you are going to use a lower version RMAN executable to backup higher
version databases then remember you are restricted to only the features available
in the database your using. But the executable you are using must be able to
handle the feature or configuration you are using.

In the above example a 10.2.0.1 rman executable tried to connect to database version 10.1.0.2 which is not supported. If we follow rule of thumb then also use 10.1.0.2 rman executable to connect to database 10.1.0.2 in order to best use of all the available features. However we can connect to 10.1.0.2 database with lower version of rman executable but that is not recommended as in that case we might be restricted to use less features.

One more thing is clear from the error message is,
"Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.1.0.0
required". So you can use any rman executable to connect to target database (which- the target database in fact 10.1g) but current RMAN executable is shown as 10.2.0.1.

Comments

Post a Comment

Popular posts from this blog

ORA-04062: timestamp of procedure has been changed

Problem Description In the database I have created one procedure named a as below. create or replace procedure a(a number) as begin insert into t1 values(1); commit; end; / Now after creating database link using remote database machine whenever I access this procedure "A" it executes successfully and I get value "1" in table t1. Like below in example where orastdby_m is the database link, shaik is the schema name and value 1 is the argument value though argument value is not used in the procedure. SQL> exec shaik.a@orastdby_m(1); PL/SQL procedure successfully completed. Now in the source database machine I changed the procedure as below. Though you can change anything like any literal; adding space or remove space. I changed value to be inserted from 1 to 2. create or replace procedure a(a number) as begin insert into t1 values(2); commit; end; / Now in the other database whenever I execute the procedure using database link it throws error ORA-04062. But subseq...
Read more

ORA-00939: too many arguments -when case arguments exceed 255

Problem Description In all Oracle 10.1g and oracle 10.2.0.1, 10.2.0.2, 10.2.0.3 whenever there is more than 255 arguments inside CASE statements then following error is returned. ORA-00939: too many arguments for function But surprisingly on Oracle 9.2 database the same code does not return any error. Cause of the Problem As we see the same code return error in 10g but it is well on 9.2. In fact this is problem of oracle 9.2 that it does not return any error. It should return error if there is more than 255 arguments inside CASE statements. In oracle 9.2 this is bug number 2909927 and this bug is fixed in oracle 10.1 and 10.2. That's why in 10.2 and 10.1 error returns if arguments exceed 255. Up to Oracle 10.2.0.3 and earlier version, the arguments of CASE statement is limit to 255 and it does not support exceed over 255 and hence error return if it exceed. However in Oracle 10.2.0.4 and later the arguments limit of CASE statement has increased to 32767. Solution of the Problem Opt...
Read more

ORA-31655: no data or metadata objects selected for job

Problem Description You are going to do data pump export operation in order to export objects based on filtering via EXCLUDE or INCLUDE parameter of expdp. In this example you wanted tables 'ACCOUNT_GROUP','ADDRESS','AREA_GROUP' and all the tables starting with word CV(like 'CV', 'CV_EXPERIENCE', 'CV_EDUCATION' etc) Your parameter file is like below. userid=smilebd/a directory=d dumpfile=b.dmp include =TABLE:"IN('ACCOUNT_GROUP','ADDRESS','AREA_GROUP')" include =TABLE:"LIKE 'CV%' " And you invoke expdp as expdp parfile=d:\parfile.txt from command line. But it fails with below message on my windows PC. C:\>expdp parfile=d:\parfile.txt Export: Release 10.1.0.4.2 - Production on Thursday, 29 January, 2009 14:53 Copyright (c) 2003, Oracle. All rights reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc tion With the Partitioning, OLAP and Data Mining ...
Read more