RMAN Catalog Version compatibility

Hi,
I have 11.1.0.7 database and RMAn repository version is 10.2.0.4 and i am receiving following error
PL/SQL package RMAN.DBMS_RCVCAT version 10.02.00.04 in RCVCAT database is too old
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of resync command at 02/01/2010 14:04:02
RMAN-06429: RCVCAT database is not compatible with this version of RMAN
So does it means i need to have RMAN repository at least 11.2.0.7? Is there a work around to resolve this issue so that i can use my current 10.2.0.4 repository for backing up my 11 g databases.
Thanks

If you have another database which is using 10.2.0.4 then using the rman executable for this database connect to your 11.1.0.7 database and recovery catalog. Then run the backup.
Regards
Asif Kabir

Similar Messages

One 8i instance and two rman catalogs 8i and 8

Can I have a single 8i instance for RMAN only with two catalogs, one for 8i and one for 8.0?

Robert,
Yes you can use a single database for 2 recovery catalogs. You can create 2 different schemas for each RMAN catalog version and each of those schemas can hold a different version of the RMAN catalog.
The only reason I can think that you would need 2 different catalogs is because you have an 8.1.X target and a 8.0.5 target? If so, make sure to have the RMAN catalog be the latest 8.1.x release.
In general, the rules of RMAN compatibility are as follows:
o The RMAN catalog schema version should be greater than or equal to the catalog database version. See "Note 1: 8.1 or Later Catalog Schemas in 8.0 Catalog Databases".
o The RMAN catalog is backwards compatible with target databases from earlier releases. See "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases".
o The versions of the RMAN executable and the target database should be the same.
Note 1: 8.1 or Later Catalog Schemas in 8.0 Catalog Databases
RMAN cannot create release 8.1 or later catalog schemas in 8.0 catalog databases.
Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases
Restore operations for an 8.0.4 or 8.0.5 target with an 8.1 or later catalog schema do not work when both these conditions are met:
The target database is mounted or open
You are connected to a recovery catalog
If any of these conditions is not met, then you can use an 8.1 or later catalog schema with an 8.0.4 or 8.0.5 target database.
Note 3: 8.1.6 Catalog Schema and Pre-8.1.6 RMAN Executable
Using a pre-8.1.6 release of the RMAN executable with recovery catalog schema of release 8.1.6.0 or 8.1.6.1 (newly created by 8.1.6 RMAN executable using the CREATE
CATALOG command) requires the following update at the catalog database:
SQL> UPDATE CONFIG SET VALUE='080004' WHERE NAME='COMPATIBLE';
null

RMAN Backup using Rman Catalog

Hi
can we take backup of oracle9i database using oracle10g RMAN Catalog?
Thanks
With Regards
OH

I guess this is related to backward compatibility support principle. Target database's controlfile and RMAN catalog is synchronized and different version may have different structure and feature. When we need to completely restore an Oracle instance from backup, RMAN catalog must be able to support target database, and it may not be possible if RMAN catalog version is lower than target database. I hope I get the message across.
Pls anybody correct me if I am wrong

RMAN catalog cleanup

Hi,
I have a scenario like to clean the rman backup information and the corresponding backups in TSM for the decomission database. I need to keep the backup which are less than a year and want to cleanup which are older than 400 days or a year.
please post your comments.
RMAN catalog version 10

Connect with your target database and recovery catalog database by RMAN.
Change your retention policy to 3 days.
RMAN > CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 365 DAYS;
RMAN > crosscheck backup;
RMAN > delete noprompt obsolete;
Also consider the backup_control_file_keep_time parameter. What is the current value? Did you change it to 365?
Regards
Asif Kabir

How to upgrade RMAN catalog from 10.2.0.4 to 11?

Hi, we are on Oracle 10.2.0.4, Solaris 5.10. Our RMAN catalog is 10.2.0.4 version and we have several 11g databases that need to connect to the catalog and obviously cannot. So we need to upgrade the catalog to 11. Does anyone have any docs on how to do it. Do I need to upgrade RMAN database to 11 via conventional upgrade and then do UPGRADE CATALOG? Really confusing, any help would be very appreciated.
Thank you!

You need to:
1 - upgrade the recovery catalog database
2 - upgrade the recovery catalog Schema
Please check the details on note *452529.1 Recovery catalog for RMAN backup*.
Normally newer databases (target) can be cataloged on previous version catalog database, but with 11g there is the bug 6756872 (RMAN REGISTER OF 11G TARGET INTO 10G CATALOG FAILS WITH ORA-04028) which force you to upgrade the catalog.
You can also review RMAN Compatibility Matrix (Note 73431.1) which has all valid version combinations.
If your scenario is simple enough, another option could be create a new 11g RMAN catalog and register there your databases, without importing data from the 10.2 catalog.
Regards.

Centralized RMAN Catalog Database

Hello,
I have two 10g R2 databases on two separate servers.
I am trying to centralize my RMAN backup by creating a RMAN_DATABASE in 11G.
- I create RMAN_DATABASE
- I created RMAN user and tablespaces
- I edited my TNSNAMES.ORA so that I could connect to my two 10G R2 databases
When I run the command:
rman catalog=rman/password@rman_database target=sys/password@10g_db1I get the following error:
Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.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
When I google the error it indicates to change the binary files, but that doesn't work either, unless I don't understand what that entails.
Any suggestions?

By saying that you have amended your tnsnames.ora to connect to the 10gR2 databases, I assume you are running the rman command on your 11gR1 server. This means that your RMAN client version is 11gR1, and your target database is 10gR2. This is not permitted, see the [compatibility matrix|http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/compat003.htm#i634479].
I suggest you try this on each of your 10gR2 servers:
1. Amend tnsnames.ora to include an entry for the 11gR1 rman_database
2. Ensure your oracle environment variables are set correctly, especially ORACLE_HOME and ORACLE_SID
3. rman target=sys/password catalog=rman/password@rman_database
This means you will be using the 10gR2 RMAN client on the 10gR2 target database which ensures no incompatibility problems. There is no issue with the fact your recovery catalog schema is at 11gR1, this is permitted to be greater than the RMAN client being used.

Can't register a database in RMAN catalog (PL/SQL package not current)

Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
$ rman catalog rman/rman target sys@MPOWER
Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
connected to target database: MPOWER (DBID=**********)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00571: ===============
RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
RMAN-00571: =================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-00904: : invalid identifier
Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
I cannot register the target database into the RMAN catalog.
I highly appretiate if you give me an advice on this.
Regards

user13064912 wrote:
Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
$ rman catalog rman/rman target sys@MPOWER
Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
connected to target database: MPOWER (DBID=**********)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00571: ===============
RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
RMAN-00571: =================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-00904: : invalid identifier
Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
I cannot register the target database into the RMAN catalog.
I highly appretiate if you give me an advice on this.
RegardsCould you try to run the rman at the target database server (MPOWER), instead of rman catalog server ant try to register your database?
Your rman client is higher than your target server. That could be the problem.
Best Regards,
Gokhan
If this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. Thanks

RMAN.DBMS_RCVCAT version 10.02.00.03 in RCVCAT database is not current

Hello RMAN experts...
Oracle 10gR2 Recovery Catalog database
Oracle 10gR2 Client database
We have just created a new Oracle 10.2.0.3 rman recovery catalog which works fine with our Oracle 9 and 10 (10.2.0.3) databases on both HP-UX and NT servers.
Problem is that I also just created a new installation of Oracle 10.2.0.4 on a new Redhat Linux 5 server but I can't seem to register my new database from this server.
First, I get the following message when I connect from the 10.2.0.4 client to the 10.2.0.3 RMAN catalog database:
$ rman target sys/$SYS catalog rman/xxxxxxx@ccrcat
Recovery Manager: Release 10.2.0.4.0 - Production on Tue May 27 09:50:14 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: ASCT (DBID=2479914243)
connected to recovery catalog database
PL/SQL package RMAN.DBMS_RCVCAT version 10.02.00.03 in RCVCAT database is not current
PL/SQL package RMAN.DBMS_RCVMAN version 10.02.00.03 in RCVCAT database is not current
Then... I'm getting the following errors when I attempt to register my 10.2.0.4 database to the 10.2.0.3 recovery catalog database.
RMAN> register database;
database registered in recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03008: error while performing automatic resync of recovery catalog
RMAN-10015: error compiling PL/SQL program
RMAN-10014: PL/SQL error 0 on line 2138 column 12: Statement ignored
RMAN-10014: PL/SQL error 306 on line 2138 column 12: wrong number or types of arguments in call to 'CHECKPROXYARCHIVEDLOG'
RMAN-10014: PL/SQL error 0 on line 1970 column 12: Statement ignored
RMAN-10014: PL/SQL error 306 on line 1970 column 12: wrong number or types of arguments in call to 'CHECKBACKUPREDOLOG'
RMAN-10014: PL/SQL error 0 on line 1810 column 12: Statement ignored
RMAN-10014: PL/SQL error 306 on line 1810 column 12: wrong number or types of arguments in call to 'CHECKBACKUPREDOLOG'
RMAN-10014: PL/SQL error 0 on line 1618 column 15: Statement ignored
RMAN-10014: PL/SQL error 306 on line 1618 column 15: wrong number or types of arguments in call to 'CHECKARCHIVEDLOG'
What can I do? I don't believe that the difference in patchset levels would matter, would it?
Please advise...
Thanks.
Ji Li

Well, out of determination, I submitted a TAR with Oracle and this is what they said.
Also note, that I did as they suggested, and now it works...
ANSWER
=======
Yes it does matter. Connect to the catalog with the RMAN 10.2.0.4 executible and execute:
RMAN> upgrade catalog;
RMAN> upgrade catalog;
Note, you must upgrade it twice.
This upgrade of the catalog will allow the 10.2.0.4 rman target to work with this catalog and will have no effect on the target databases wthich are of an eariler version.
NOTE, however, that when I checked the recovery catalog and also the registry, all componets in the recovery catalog are still v.10.2.0.3.
Ji Li

10G RMAN catalog in 9i

Hi,
I can't find this information in any documentation, so this is the best place for it.
Can we create a 10g RMAN catalog on 9i database? If no why? If yes, then is
there any known issue/problem with this?
Thanks....

Hi,
You can create !!
But you might experience the problems, with Backward compatability..
I suppose.. that..
Thanks
Pavan Kumar N

Howto: RMAN catalog backupset in different location

Hi,
How can I tell RMAN catalog that the location of backup set has changed.
For example: after my RMAN backup all my backup pieces went to C:\first_location\
directory. I am using a catalog while running backup.
Now I moved the backup pieces to D:\new_location\ directory. Say C:\first_location\ directory is no longer for some reason. How do I tell my catalog that the backup pieces about the new location D:\new_location\
Catalog, Rman, database all in 10.2 version.
thank you in advance

Thank you for your response to my question.
Can someone help me with syntax and usage of new location of backup pieces in a backup set to be reflected in my catalog. Catalog, target and rman all 10g version.
thanks in advance

RMAN catalog Downgrade from 11gR1 (11.1.0.6.0) to 10gR2 (10.2.0.4)

I am in the process of downgrading rman catalog from 11gR1 (11.1.0.6.0) to 10gR2 (10.2.0.4). Using expdp/impdp we migrated the rman schema from 11g to 10g. I am able to connect to 10g catalog now. but if i run any command it gives following error.
./rman target sys
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Feb 16 11:21:11 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
target database Password:
connected to target database:
RMAN> connect catalog rman/*******@rman
connected to recovery catalog database
RMAN> show all ;
RMAN configuration parameters for database with db_unique_name NACC are:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of show command at 02/16/2010 11:21:34
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20299: DBMS_RCVMAN package not compatible with the recovery catalog
RMAN> exit
Have i missed anything which has to be done .
Thanks
Ajeet

Hi Tycho ,
Thanks for your help and suggestions . What i did is i migrated the rman catalog from 11gR1 (11.1.0.6.0) to 10gR2 (10.2.0.4) then connected rman catalog from 11gR2 Client which is the highest version available and then did the following.
RMAN> upgrade catalog;
recovery catalog upgraded to version 11.02.00.01
DBMS_RCVMAN package upgraded to version 11.02.00.01
DBMS_RCVCAT package upgraded to version 11.02.00.01
RMAN>
Now i am able to connect directly and take backup's from 11gR2 , 11gR1 and 10gR2 clients respectively. I also tested the backup's from grid control which are working fine.
Currently my rman catalog database is 10.2.0.4 and my rman catalog schema is 11.02.00.01.
Thanks for everyone's help.
Ajeet
Edited by: user12169940 on Feb 17, 2010 4:02 AM

Creating RMAN catalog. Are these steps correct?

Are these steps to set up the RMAN catalog correct?
I.
The following two databases are the target databases which needs to be backed up.
1. a 11.1.0.7.0 database
2. a 10.2.0.1.0 databaseII.
Catalog schema in a 10.2.0.4.0 database called catdb.
III.
I am going to use the RMAN client(10.2.0.1.0) in my laptop (Windows Server 2003).
CATALOG schema creation
=======================
To create the Catalog Database (10.2.0.4.0), this what i am going to do in catdb
 a. create tablespace CAT_TBS
 b. CREATE USER rman_cat_schema
 IDENTIFIED BY rman_cat_schema
 DEFAULT TABLESPACE cat_tbs
 TEMPORARY TABLESPACE temp
 QUOTA UNLIMITED ON cat_tbs;
 c. GRANT create session TO rman_cat_schema;
 d. GRANT recovery_catalog_owner TO rman_cat_schema;
 e. GRANT execute ON dbms_stats TO rman_cat_schema;
 f. Invoke the RMAN binary from my laptop :
 C:\>set ORACLE_SID=catdb
 C:\>rman catalog rman_cat_schema/rman_cat_schema@catdb log=catalog.log
 Hopefully Catalog will get the created at catdb .
Registering the database
=========================
To register the database,this is what i am going to do.
 a. Add the Tns Entry about the catdb in tnsnames.ora file of the target database
 b. Log in to target database's machine and invoke the RMAN executable in the target database. 
 $ export ORACLE_SID=oraprod314
 $ rman TARGET / CATALOG rman_cat_schema/rman_cat_schema@catdb
 c. Then i can give the REGISTER DATABASE command. like
 $rman > register database;
 Edited by: Citizen_2 on 14-Sep-2009 11:46

Yes, You can connect to RMAN catalog using a lower version client. see this.
SQL> conn rman/rman@mycatdb
Connected.
SQL> select * from rcver;
VERSION
11.01.00.06
SQL>
rman
Recovery Manager: Release 9.2.0.7.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN> connect target /
connected to target database: STSTDB (DBID=2045697105)
RMAN> connect catalog rman/rman@abcd.
connected to recovery catalog database
RMAN>
You can take the backups and do recoveries. But, if you want to achieve certain features of the recovery catalog of higher versions to backup / recover your database, you better use the right RMAN client which allows the features to use.
It is always advisable to use the RMAN Client same as the database version you want to backup to avoid any confusions.
Hope it is helpul.
Regards
Edited by: vasu77 on Sep 15, 2009 10:01 AM
Edited by: vasu77 on Sep 15, 2009 2:11 PM

RMAN Catalog Upgrade Understanding.

Hi,
We just upgraded our target database from oracle version 9.2.0.7 to 9.2.0.8 and our catalog database is still in 9.2.0.7 . Do we need to upgrade the recovery catalog schema in the catalog database If so then how to do that.
I tried running upgrade catalog command on the recovery schema of the catalog database and it is upgrading to the 9.2.00 version packages.
reldb3d:instra /opt/app/oracle/product/9.2.0.8/rdbms/admin> rman catalog instra/[email protected]
Recovery Manager: Release 9.2.0.8.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to recovery catalog database
RMAN> upgrade catalog;
recovery catalog owner is INSTRA
enter UPGRADE CATALOG command again to confirm catalog upgrade
RMAN> upgrade catalog;
recovery catalog upgraded to version 09.02.00
DBMS_RCVMAN package upgraded to version 09.02.00
DBMS_RCVCAT package upgraded to version 09.02.00
Right now I am skeptical is it the correct way of upgrading the catalog schema in the catalog database.
Any suggestions/advice will be highly appreciated.
Thanks,
Raheem

The schema version (or the objects therein) is different from the version of the database in which the rc schema resides. As long as oracle wouldn't force you to upgrade the database, upgrading the schema is enough. The same applies to the the repository database for grid control. The version of the grid repository schema can be different from the version of the database software.
Whatever you did is correct.

Query RMAN catalog to view my controlfile backup in backup piece

version: 11.1.0.7
We need to restore an year old database and its backup is availble in TAPE, RMAN directly takes backup to TAPE.
we have dropped the database, Now there is a requirement to restore the database.
we Know DBID, I can restore the db once i can restore the contolfile.
However we did not have controlfile auto backup. whenever there is FULL/incremental backup cotnrolfile is included in that backup. now we have the rman catalog for that database. so How I can query rman catalog to find which backup piece containing the latest controlfile? once we know the backuppiece info, we can restore controlfile from that piece
any help on this?

user8860934 wrote:
version: 11.1.0.7
We need to restore an year old database and its backup is availble in TAPE, RMAN directly takes backup to TAPE.
we have dropped the database, Now there is a requirement to restore the database.
we Know DBID, I can restore the db once i can restore the contolfile.
However we did not have controlfile auto backup. whenever there is FULL/incremental backup cotnrolfile is included in that backup. now we have the rman catalog for that database. so How I can query rman catalog to find which backup piece containing the latest controlfile? once we know the backuppiece info, we can restore controlfile from that piece
any help on this?Connect with recovery catalog through rman and
set dbid <yourdbid>
list backup of controlfile;In this case you will see all backups of controlfile.And according time this backup you can restore database using
rman>restore controlfile from 'backupset_location';

Backing up the RMAN catalog database

Version: 10.2.0.1.0
We have created a database to host our RMAN catalog. This catalog holds backup info plus RMAN stored scripts for 5 production databases . Now, we need to backup this RMAN catalog database.
I am going to use the control file as the catalog (ie. NOCATALOG) for our RMAN catalog database. This should be fine. Right? Any best practices i should follow regarding this?

Sometime back I had the same question.
What I decided was cold backuo and RMAN using the control file. (A Belt-and-suspenders approach)
I also do an export daily after all the other backups are done.
In addition I keep an information on it, location and size of all files, a current PFILE (it does not change much), what patches etc.
Given its tiny footprint it would be easy to rebuild given all this.

RMAN Catalog Version compatibility

Similar Messages

Maybe you are looking for