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.

Similar Messages

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.

How can i get no of database registered to RMAN catalog database.

I want to know that how can I know that no of database are registered to particular RMAN repository database.
And also i want to upgrade my reposiotry catalog as we are upgrading our database to 11g
Kindly help me .

Hi,
Just connect to the catalog database as "rman" user and query the rc_database view.
sqlplus <rman_user>/<rman_user_passwrd>@<catalog_db>
SQL>select * from rc_database;
user11958935
Handle: user11958935
Status Level: Newbie
Registered: Nov 20, 2009
Total Posts: 72
Total Questions: 29 (22 unresolved) Please consider closing the unanswered questions and keeping the forum clean.

Rman catalog database

Hi,
i have few questions..
If we want to use a recovery catalog database ...for rman..
can it be different version of our targer database ...we can use lower,,heigher.
version .... ?
how can we configure tivoli tape for backup purpose with our database..?
any idea ..
thanks

oradba11 wrote:
Hi,
i have few questions..
If we want to use a recovery catalog database ...for rman..
can it be different version of our targer database ...we can use lower,,heigher.
version .... ? In general you would use the highest version of the RMAN client and the RMAN recovery catalog for all lower database version. Since RMAN's active code is inside the database kernel, the RMAN command line interface is used to issue the command to the database. This allows a higher version of RMAN command line to connect and issue backup & recovery commands to older versions. Look at the Backup and Recovery 'Reference' manual for command compatibility.
>
how can we configure tivoli tape for backup purpose with our database..?RMAN needs a 'Media Management Library', which is basically an external driver, to talk to the tape system. Normally you purchase that from a third party (BMC, Veritas, Tivoli) or you could purchase Oracle Secure Backup to act as a complete backup management system which happens to include the RMAN MML. You want to check http://www.oracle.com/technology/deploy/availability/htdocs/RMAN_Overview.htm and look at the Backup Solutions Program (BSP).
Some people think MML tends to be expensive and direct-to-tape tends to be slow. So some organizations have taken the approach of RMAN to staging disk and standard OS tape backup from staging disk. (I've even seen organizations create an Openfiler-based iSCSI NAS with a few TB of SATA-based RAID (10) for under $2K and attach that as the disk backup. Slower than SAN, faster than tape, and very inexpensive.)

Best strategy for backing up the rman catalog database

I have seen people do
1. full export
2. backup with control files
3. put a repository in another database and cross backup
What do you use?
I am in 10.1, but this is a general question.

Hi,
1. full export
This is a logical backup - don' treat it as permanent - it's not physical backup for recovery scenarios.
2. backup with control files
In the case of loss of control files, its can be used for that.
3. put a repository in another database and cross backup
It's to persits the data Base backup histories in another database, gives the facility to clone/ re- build the DB to different node - in terms of crashes.
For stratergy you need to checl with your SLA's and primarly refer to ORACLE Doc's you can able know the pro's and con's. Based on that you jutify what better suits your Application.
- Pavan Kumar N

Create a clone database form rman catalog !

Dear Friend ,
I have a rman catalog database . I am using this rman catalog for against a database name 'testdb' . Everyday I take rman full backup of the testdb using the catalog database .
Now I create a another database which will be the clone of the testdb . I want to create it using that rman catalog database . Can I create a new database using the catalog database ?
If yes, then plz help me to give some directions .....

Check here:
[http://www.shutdownabort.com/quickguides/clone_rman.php]
[Duplicating a Database with Recovery Manager|http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmdupdb.htm#441628]
Oracle documentation Link added.

How to setup catalog database for backup

In order to use RMAN,
catalog can be put in a controlfile, one of the database if we have many database, or in a special catalog database, is that right?
So, I am wondering about the special catalog database, should we setup a totally new oracle database, and then setup catalog in it? Am I right?
Edited by: user8117130 on Jun 19, 2009 10:21 PM

Hi,
http://mehrajdba.wordpress.com/2008/12/23/rman-catalog-database-creation/

Need a create db script to manually create a 10g rman catalog db on unix

Hi, Gurus:
I would like to manually create a rman catalog database (Oracle 10g) on a HP-UX environment. Could anyone share a sql script to do that?
It is going to be used to backup about 15 databases directly to tape and the retention policy is going to be 35 days. How big the database should be?
Thanks in advance.

I can't find any documentation supporting Oracle support's theory.And who writes the Oracle documentation? People in this forum?
You got the "Best Practice" advise.
If you have rman catalog on the same server or on the same database, it is like storing your backup on the same server you took it from.
So, the idea od RMAN catalog is to have your catalog available for any recovery. If you cannot recover your recovery catalog, then you are better off using the controlfile as the repository.

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

Rman: target database upgradation

hi,
My rman catalog database is 11.2.0.1 and target database is 10.2.0.4 (in windows server).
Now i have upgraded my target database to 11.2.0.1 from 10.2.0.4 . After upgradation backup is going fine.
My doubt is, whether the backup will be a valid one, or i have to unregister and register again the target database.
Please clarify my doubt.
Thanks & Regards,

Backup will be a valid one. No need to register again.
Regards
Asif Kabir

Restore; RMAN catalog simulation

Hi,
I have a database and a backup on tapes done with rman. I would like to test the restore. For this I can export the database on a new computer. But how to simulate the use of Rman catalog.
Thank you,
Mihaela

hi,
If your target or Rman Catalog database are some then you can export catalog tablespace and import in your another computer where your transfer your target database.
regards
Taj

Error while registering RMAN from primary to catalog database

Hi all,
Here we have a 10g dataguard environment with db1(db_unique_name) as primary and db2(db_unique_name) as physical standby database. Also we configured one schema on a third machine as catalog database using following steps.
The steps executed in catalog database(appsdb):
SQL> create tablespace rmancatlog_tbs datafile '/u01/app/oracle/oradata/NEW/rman_catalog.dbf' size 500M autoextend off extent management local segment space management auto;
SQL> create user rman identified by oracle
2 default tablespace rmancatlog_tbs
3 quota unlimited on rmancatlog_tbs
4 ;
SQL> GRANT connect, resource, recovery_catalog_owner TO rman;
RMAN> create catalog;
recovery catalog created
Added tns entries of catalog database in primary and standby. Then from primary database we tried to register to catalog database. It is showing that it is registering. But every query afterwards in rman is throwing the error. Below are the steps and error:
[oracle@db1 ~]$ rman target sys/oracle catalog rman/oracle@appsdb
Recovery Manager: Release 10.2.0.3.0 - Production on Mon Aug 13 21:39:32 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: NIOS (DBID=1589015669)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
RMAN> report schema;
Report of database schema
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 10/08/2012 06:16:06
RMAN-00600: internal error, arguments [8201] [] [] [] []
Can anyone help regarding this error?
Thanks in advance.

on resync catalog it is throwing no output or error.
but it shows same error afterwards.
RMAN> resync catalog;
RMAN> report schema;
Report of database schema
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 10/09/2012 03:55:53
RMAN-00600: internal error, arguments [8201] [] [] [] []

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

Unregistering of a database from RMAN Catalog

Hello,
We had set up RMAN backup though RMAN Catalog for one of our database.
We later decided not to take the backups of this particular database. One of the DBA did something but what we can see now is that -
1. Target database is not registered in the catalog so no information can be gathered rman prompt after connecting to catalog through target database
2. But the recovery catalog "rc_backup_datafile" is showing as if it has old backups
We know that the tapes don't have the backup of this database.
Question - How to remove information from recovery catalog for a database in such a situation where although the database is not registered in the catalog but somehow the information related to old backups still persists in the catalog tables.
Thanks!

Thanks Tycho, for my purpose DBMS_RCVCAT.UNREGISTERDATABASE worked fine.
I have another question though -
We have compressed backup for one of the database/
If I look at backupset by executing "list backupset xxxxxxx;" command it shows the correct compressed value (in GB) of the backup set.
BUT when I look at the rc_backup_datafile table of the rman catalog for the size of of the backupset, it shows the uncompresses size of the backupset. I am using following query -
select BS_KEY,SUM(blocks*block_size)/1024/1024/1024 GB from rc_backup_datafile where DB_NAME='CCSTG04' and BS_KEY=1 group by BS_KEY;
Question - How to check the compressed size of the backupset from the Catalog tables/views?
Thanks for your help on this!
Thanks!
,

How to get RMAN catalog information from Target database?

Hi,
How to get RMAN catalog information from Target database because i don't know about catalog database? is it possible?
Thanks

If you run RMAN backups of a target database using a Catalog schema in another database, the target is not aware of the catalog.
The RMAN backup script would have the connection identifier for the Catalog.
Hemant K Chitale

Centralized RMAN Catalog Database

Similar Messages

Maybe you are looking for