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.

Similar Messages

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

Photoshop Elements 10 will not allow me to back up the entire catalog.

Photoshop 10 will not allow me to back up the entire catalog. During its initial set up, when it runs the space needed, it stops at 18% and will not go beyond that
Here is what I am doing. In Elments Orgainizer, I am going to FILE, then selecting Back Up Catalgo to CD,DVD or Hard Drive, then I select- Full Back Up, then it goes to Calculate Total Media Space and that is where is stops at 18%

Thanks for the response
My OS is Win 7 Home Prem
The catalog is over 60GB and over 31,000 images
There are only a few videos in the catalog
I am backing up to a hard drive that is a 2TB drive
I can not even get to select the drive, as the system stops as it calculates the amount of space needed.

Query to identify the recovery catalog database name from target database

Hi,
How to get the recovery catalog database name from the registered target database?
i dont know my recovery catalog database for my target database.
I know we can use the query
select * from rc_database;
from recovery catalog database to know all the registered database with the recovery catalog but I want to know is there any way or query to identify the recovery catalog database name from target database to which the target database is registered
With Regards
Boobathi P

You can check the backup scripts which you use to backup your target database to get the catalog database name.
And check the corresponding connect string in TNSNAMES.ORA file or tnsping to get the server details of the catalog database.
Edited by: gopal on Apr 12, 2013 12:59 PM

Backing up an RMAN Catalog/OEM Repository

This may be a supid question but I will ask it nonethelss.
I have an RMAN catalog/OEM Repository which has never been backed up.
Can I use register this (RMAN catalog/OEM Repository) DB within the catalog on the same instance and then back it up as well?
Tks & Regards

Hi 860user6196,
And how are you going to recover your database in case of a disaster?
Clearly the catalog won't be available...
Regards,
Tycho

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.)

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.

Wrongly created the rman catalog

Hi friends,
in my prod server i created catalog user and catalog tablespace and am not create catdb.
i connect to target database and I took backups.
is it valid backups?
if not what can I do?
regards

You may want to follow these instructions for details on the process:
Step 1. Creating a Recovery Catalog
Step 2. Managing Target Database Records in the Recovery Catalog
Again, you should NOT create the recovery catalog in your target (production) database.

How to recover the rman catalog

all,
I have created a recovery catalog and back it up using the control file and the nocatalog option - see below
rman nocatclog target=rman
run{
backup database;
backup (archivelog all delete input);
How do I recover the catalog if it dies?
rgds
alan

hi,
thanks for the response. I will give it a try, but at a cistomer site doing this and they have no test server to try it on. Production only so need to be sure of what is going to happen.
rgds
alan

I'm having trouble after editing in PS where my photo are not added back to the current catalog

I like to use the "Edit in" Photoshop feature of Lightroom, but after moving to CC...My photos after saving them after correcting in PS are not returned into the catatlog. I've been having to importment the edited photo back into lightroom from the finder folder..I remember prior to CC my photos whould return to the strip with Edit.tiff, not any more..?

Reset your preferences file: Resetting (or 'Trashing') the Lightroom Preferences file - Lightroom Forums
Report back if that doesn't work.

What's the recommended guideline on backing up a recovery catalog?

while I understand "Benefits of Using the Recovery Catalog as the RMAN Repository" as stated in
http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmquick.htm#442214
as well as things to take note if using control file as the sole rman repository,
as stated in "Monitoring the Overwriting of Control File Records" in http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmrepos.htm#446924
I do not understand why in Backup and Recovery Advanced User's Guide
http://download.oracle.com/docs/cd/B14117_01/server.101/b10734/rcmrepos.htm
"Back Up the Recovery Catalog Often"
Even if you have to restore the recovery catalog database using a control file autobackup, you can then use the full record of backups in your restored recovery catalog database to restore the target database without using a control file autobackup for the target database.
=>probably implies that we can use another recovery catalog let's call it backupbackup to restore the recovery catalog
"Choosing the Appropriate Method for Physical Backups"
Follow these guidelines when developing an RMAN backup strategy for the recovery catalog database:
* Run the recovery catalog database in ARCHIVELOG mode so that you can do point-in-time recovery if needed.
* Set the retention policy to a REDUNDANCY value greater than 1.
* Back up the database onto two separate media (for example, disk and tape).
* Run BACKUP DATABASE PLUS ARCHIVELOG at regular intervals, to a media manager if available, or just to disk.
* Do not use another recovery catalog as the repository for the backups.=> this contradicts the previous statement
* Configure the control file autobackup feature to ON.
so may I know what's the recommended guideline on backing up a recovery catalog? should we use another recovery catalog to keep the rman repositories of the the main primary catalog or just use a control file autobackup feature?
thanks

I understand the question and the confusion.
Please note, however, that this forum is for discussing problems and errors with the documentation in general. Your question is related to a specific product and is, as far as I can tell, not a note about a documentation error or a correction.
The appropriate place to discuss this is the Database (General) forum or - perhaps surprisingly - the RMAN forum. These can both be found by
1) Clicking on the 'Forum Home' link at the top of this page;
2) Scrolling down to the category 'Database' (a category is identified by a special row format that does not list the number of topics)
3) Expanding the category by clicking on the 'More ...' link.
4) Scrolling down to the "Database - General" or "Recovery Manager" forum and clicking on it's link.
Note that forums have a search function that may be used to find answers if someone has already asked a similar question.

RMAN catalog fails to show target database information when in nomount mode

Hello everyone, I am trying to restore a dev. database from its own backup taken a week back. The DB is in noarchivelog mode and recently 2 of the datafiles were removed from the files system and thus the need to restore the DB from its backup. However rest of the files and control files are intact.
Now, when I put the database in mount mode and connect to the catalog then I can see the DB's incarnation;
:->rman catalog cde01_rman4/xxxxxxx@prman10g target /
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 11 13:54:40 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: EGVBFI2 (DBID=4238332493, not open)
connected to recovery catalog database
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
84789 84883 EGVBFI2 4238332493 PARENT 2478183021921 17-JAN-04
84789 84790 EGVBFI2 4238332493 CURRENT 2498633332010 10-OCT-07
RMAN>
However I am not able to see DB incarnation in the RMAN catalog if I put the DB in nomount mode (which is required to recover DB);
:->rman catalog cde01_rman4/xxxxxx@prman10g target /
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 11 13:58:29 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: egvbfi2 (not mounted)
connected to recovery catalog database
RMAN> list incarnation;
RMAN>
Please advice?
Thanks,
Jairaj

Hi,
You won't be able to see incarnation information when the DB is in "nomount" since the incarnation is written in the control file. I don't think the catalog has this information.
Anyway, in order to restore datafiles, the instance must be mounted, so you should be OK.
Mount the instance and just restore the datafiles.
Liron Amitzi
Senior DBA consultant
link: [www.dbsnaps.com]
link: [www.obriumsoftware.com]

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

Backing up the RMAN catalog database

Similar Messages

Maybe you are looking for