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.

Similar Messages

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.

Why use RMAN CATALOG ?

Hi,
Anybody tell me why use RMAN CATALOG and what benifits if i have create catalog ?

No we have to configure it. I see. But did this user understand that when you quoted my reply ? We need to understand that a lot of users who post here need help and may not have the level of knowlege you have. So, a response like that adds more problems to the one they already have.
So even if you are using nocatalog, if it is not configured to auto backup and it is not backed up, you can still loose your RMAN 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 catalog and Target database

Hi All,
Please clarify my below doubts.
We have one server "server1" with oracle (catalog database) version 10.2.0.1
I have server "server2", and we have four oracle homes with four oracle users.Each oracle home consist of one database. all database are with 10.2.0.3 version.
All these databases registered with the above catalog database.
1 -> Can we register databases with a lower catalog database.
2 -> Now we are upgrading one database to 10.2.0.5 (in server2), in upgrade step we need to action step -: catalog upgrade. If we run this command actually what will be the result?
3 -> We are upgrading only one database in server2. remaining 3 database are in the version 10.2.0.3, upgrade catalog command will upgrade catalog database to 10.2.0.5 version, am I right?
4 -> Here do I need to run upgrade catalog ?
Thanks,
Asim
Edited by: user229955 on Feb 25, 2012 4:18 PM

Please refer this MOS document *RMAN Compatibility Matrix [ID 73431.1]*
You would surely get your answers if you mark your previous questions as answered rather than keeping it open.

Migrate Rman Catalog over cross platform's

I need some suggestion for migrating Rman Catalog...
Current Rman Catalog: 10gR2 on HPUx and would like to migrate and upgrade to 11g on Linux....Any suggesions...
My thoughts: exp and import schemas from hpux to linux 10g -10g and upgrade 10g catalog to 11g on new linux server....
Any help would be appreciate.....

There is "NO UNREGISTER" option...
NO UNREGISTER Forces RMAN to keep imported database IDs in the source catalog schema. By default, the imported database IDs are unregistered from source recovery catalog schema.
-------------------------------------------------------------------------

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.

SQL Reports Bad Idea Against RMAN Catalog?

11.2.0.1 SPARC 64
We use OEM to manage/execute our backups. The MML is NetBackup. One downside to this is that the "job" within OEM executes the backup for 20+ databases. In a serial fashion the backups occur in NetBackup...but most are queued - they throttle through and over time they complete. To this end, we have no way of seeing the true backup duration. We know the rman start and completion times, but they're not "actual."
I started looking at creating a sql statement/report/[pl/sql] block that would give us the granular informatin on the true timings of the backup "pieces" as they relate to a "set."
Research out on the wire shows a number of high level solutions, but nothing to which a report shows the data files, etc. Usually when I see this I start to question..."hey, is this even a good approach?"
I do realize that through the RMAN utility there are a number of reports which are available...this post, however, is focused on the idea of sql reports against the rman catalog.
Any advice would be welcome.
Conceptual report:
-> INCREMENTAL LEVEL 0
--> BACKUP SET
---> BACKUP PIECE
----> HANDLE, TAG, DATAFILE, START, COMPLETION
I'm NOT looking for the sql...I can work that out, I just want to know if this is a smart approach or best to stay out of the catalog.
-abe
Boulder, Colorado
Edited by: user10863631 on Mar 10, 2011 7:43 AM
Edited by: user10863631 on Mar 10, 2011 7:56 AM

I think this is the wrong forum for such a question. The Database - General (General Database Discussions might be better suited. Or maybe the RMAN forum (Recovery Manager (RMAN)

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

Question: Which is better and why....RMAN catalog or Flashback Recovery

Hey All,
Newly testing and reading up on 10g. I am on information overload and would appreciate pro's advice on which to choose and why.
Thanks,
d.

Different things, not necessarily alternative. That is, RMAN catalog is normally (at least should be) on another machine, and does not contain physical backups, but only information about them : physical backups are normally stored on external devices, like tapes.
Flashback Recovery technique is based on Flashback logs in Flash Recovery Area, which is a disk area on local machine, and so cannot be unlimited.
Therefore, Flashback Recovery is much faster than Media Recovery, since you don't need to restore anything, but you have limits in using that : your disks size.
On the other hand, RMAN backups are safer, being physically elsewhere.
See http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14220/backrec.htm#g1023042

To Find the instance name in RMAN catalog

Hi ,
I have rman catalog which got registered 150 databases. Am able to get the dbname,id for the 150 databases but not able to get the server name (host name) of the correspoding databases in catalog views as well as in db views.
Kindly revert us if you know any other analyisis or way to find the server names.
Regards
Krishnan

What does RMAN care if RAC is involved or not?
Oracle provides RMAN for backing up and restoring the database. RMAN enables you to back up, copy, restore, and recover datafiles, control files, SPFILEs, and archived redo logs. RMAN is included with the Oracle server and it is installed by default. You can run RMAN from the command line or you can use it from the Backup Manager in Oracle Enterprise Manager. The procedures for using RMAN in RAC environments do not differ substantially from those for Oracle single-instance environments. Refer to the Oracle Backup and Recovery documentation set for more information about single-instance RMAN backup procedures.

A possible bug in RMAN CATALOG command in 10g on Linux (SLES9 SP3)

Hi,
I ran into this issue while using RMAN command "CATALOG DATAFILECOPY <filename> TAG <tagname>". In this instance, RMAN is actually trying to write 8K data at block 1. Since a copy is being cataloged, it doen't make any sense to modify it. Please note that this modification doesn't happen without TAG option. This behavious doesn't seem to be present on Oracle 9 on Solaris 8. For more details, please check the following thread:
help with RMAN CATALOG command
Thanks,
Raghu.

Hi Steve,
Unfortunately this is a bug, bug 3612370 in fact. I've published the bug so that it can be tracked via metalink if you have a support contract.
The bug is as you suspected with JDev's parse of the modules. We don't have a workaround at the moment but I'll post here again if we make any progress.
Thanks for reporting this,
Geoff
JDev Test Team

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!
,

Schedule a crontab in rman catalog

Hi,
I am trying to schedule a crontab in rman catalog side but it wasn't work.
I prepared a scripts and I dont know why it was not worked.
Please can anyone tell me how can I schedule my crontab in rman.
The scripts is this,
00 01 * * 0 ksh /u01/app/oracle/product/10.2.0/bin/ora_rman.sh >/dev/null 2>&1
vi ora_rman.sh
ORACLE_SID=p001
ORACLE_BASE=/orahome/p001
ORACLE_HOME=$ORACLE_BASE/10.0.2
PATH=$ORACLE_HOME/bin:$PATH
$ORACLE_HOME/bin/rman catalog rman/rman target sys/sys$pwd@p001 /u01/app/oracle/product/10.2.0/bin/ora_rman.sh <<EOF
run {
backup incremental level 0 as compressed backupset database plus archivelog;
delete noprompt archivelog all completed before 'sysdate-7';
00 19 * * * ksh /u01/app/oracle/product/10.2.0/bin/ora01_rman.sh >/dev/null 2>&1
vi ora01_rman.sh
ORACLE_SID=p001
ORACLE_BASE=/orahome/p001
ORACLE_HOME=$ORACLE_BASE/10.0.2
PATH=$ORACLE_HOME/bin:$PATH
$ORACLE_HOME/bin/rman catalog rman/rman target sys/sys$pwd@p001 u01/app/oracle/product/10.2.0/bin/ora01_rman.sh <<EOF
run {
backup incremental level 1 as compressed backupset database plus archivelog;
delete noprompt archivelog all completed before 'sysdate-7';
waiting for your replies,
Thanks & Regards

Here's my working stuff:
I use an .env file. Here's the crontab entry, script and env file.
00 16 * * 0-6 /u01/app/oracle/dba_tool/PRIMARY/db_rman_full.sh > /tmp/PRIMARY_rmanfull.out
#!/bin/bash
# Name: db_rman_full.sh
# Purpose: Database rman backup
# Usage : db_rman_full <DBNAME>
. /u01/app/oracle/dba_tool/env/PRIMARY.env
echo "Starting RMAN..."
$ORACLE_HOME/bin/rman target / catalog <catalog_user>/@<catalog_db> << EOF
run { allocate channel d1 type disk;
backup full as compressed backupset
database plus archivelog;}
crosscheck backup;
delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-5';
DELETE noprompt BACKUP COMPLETED BEFORE 'SYSDATE-2' DEVICE TYPE DISK;
exit
EOF
echo `date`
echo
echo 'RMAN Full on PRIMARY Complete'
env
ORACLE_BASE=/u01/app/oracle
ULIMIT=unlimited
ORACLE_SID=PRIMARY
ORACLE_HOME=$ORACLE_BASE/product/11.2.0
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
LIBPATH=$LD_LIBRARY_PATH:/usr/lib
TNS_ADMIN=$ORACLE_HOME/network/admin
PATH=$ORACLE_HOME/bin:$ORACLE_BASE/dba_tool/bin:/bin:/usr/bin:/usr/ccs/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:/usr/lbin:/GNU/bin/make:/u01/app/oracle/dba_tool/bin:/home/oracle/utils/SCRIPTS:/usr/local/bin:.
export TERM=vt100
export ORACLE_BASE ORACLE_SID ORACLE_TERM ULIMIT
export ORACLE_HOME
export LIBPATH LD_LIBRARY_PATH ORA_NLS33
export TNS_ADMIN
export PATH
----If you find this helpful please mark it so----

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

RMAN Catalog Upgrade Understanding.

Similar Messages

Maybe you are looking for