Recovery catalog, target database.

Hello all,
I have a question concerning recovery catalog.
Can i use the same database as recovery catalog and target database?
Let us say that i have a database orcl, can this database be the target and the recovery catalog at the same time ? is there any disadvantages?
Regards,

NB wrote:
Hello all,
I have a question concerning recovery catalog.
Can i use the same database as recovery catalog and target database?
Let us say that i have a database orcl, can this database be the target and the recovery catalog at the same time ? is there any disadvantages?Yes you can use the same database as the recovery catalog but that's going to be a wrong decision. Think about this, you have lost your target database and since you had your recovery catalog also stored in it, now that's also gone! So a good thing or bad thing it would be ?
Edit:
Please read the same from the docs,
http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmcatdb.htm#CHDECBEH
Do not use the target database to be backed up as the database for the recovery catalog. The recovery catalog must be protected in the event of the loss of the target database.Aman....
Edited by: Aman.... on Aug 7, 2011 4:26 PM

Similar Messages

Connecting to Catalog & Target Database

I am trying to register a target database with a recovery catalog. RMAN database and the catalog table space were created. When trying to connect to target with the SID set to the instance name and simply connecting as username/password, I am getting connected to the target. If I try to connect using the connect string, I get the following error
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database: ORA-12154: TNS:could not resolve service name
But the TNS names have been properly configured and I am able to connect from sql*plus using the connect string.
Similarly I set the SID to RMAN database and try to connect catalog with username/password I am able to connect to Catalog and if I use connect string for the target, I am getting the same error as mentioned above.
I really do not know, How to resolve this and to connect to Target and RMAN databases simultaneously.

I suggest you do the following to see if the connect strings are really working, either:
1) Change ORACLE_SID to be of the catalog database, now do:
% sqlplus "<user>/<pwd>@<target string> as sysdba"
Does that work? If as I suspect it does not work or connects you to the catalog database (not the target), then it is a missconfiguration of the network files.
2) Do the same for connection to the catalog, set ORACLE_SID to be the one of the target database and do:
% sqlplus "<user>/<pwd>"
Does that connects you to the catalog?

Config recovery catalog database

dear all.
i had read several documents about "create recovery catalog", but all of that start with statement
CREATE TABLESPACE
...and continue with CREATE USER, etc.
I want to create a NEW database for recovery catalog, this database what characteristics must to have ?? Anyone have a link or document where explain me how to create a database (only i need database creation) for recovery catalog.???
thanks
The version is ORacle 10gr2

hi,
the recovery catalog is just a normal database with a schema called rman or whatever you choose.
it should ideally be on a separate server to your target database. The RMAN database as with any other database should have multiplexed control files and redo files.
schema creation assumming windows O/S
-- Create tablepsace to hold repository
CREATE TABLESPACE "RMAN"
DATAFILE 'C:\ORACLE\ORADATA\W2K1\RMAN01.DBF' SIZE 6208K REUSE
AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
-- Create rman schema owner
CREATE USER rman IDENTIFIED BY rman
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE rman
QUOTA UNLIMITED ON rman;
GRANT connect, resource, recovery_catalog_owner TO rman;
then create the recovery catalog
C:>rman catalog=rman/rman@w2k1
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to recovery catalog database
recovery catalog is not installed
RMAN> create catalog tablespace "RMAN";
recovery catalog created
RMAN> exit
Recovery Manager complete.
C:>
then register your database
C:>rman catalog=rman/rman@w2k1 target=sys/password@w2k2
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: W2K2 (DBID=1371963417)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
full resync complete
RMAN>
let us know how you get on.
rgds
alan

RMAN-20001: target database not found in recovery catalog

I am practicing loss off all control files. I have rman catalog backups which are set to autobackup controlfile. So far I did this.
RMAN> startup nomount;
Oracle instance started
Total System Global Area 209715200 bytes
Fixed Size 1272864 bytes
Variable Size 155190240 bytes
Database Buffers 50331648 bytes
Redo Buffers 2920448 bytes
RMAN> restore controlfile from autobackup;
Starting restore at 08-SEP-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
recovery area destination: /u02/flash_recovery
database name (or database unique name) used for search: TEST
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /u02/flash_recovery/TEST/autobackup/2009_12_09/o1_mf_s_705171034_5l0kgv4o_.bkp
channel ORA_DISK_1: control file restore from autobackup complete
output filename=/u02/control_files/TEST/control02.ctl
output filename=/u03/oradata/TEST/control03.ctl
Finished restore at 08-SEP-10
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 09/08/2010 14:54:50
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog
I am assuming this has something to do with DBID but ... I don't have it and I don't know how to find it.

Hi BelMan,
Here is output
BS Key Type LV Size Device Type Elapsed Time Completion Time
56869 Full 11.20M DISK 00:00:00 08-SEP-10
BP Key: 56871 Status: AVAILABLE Compressed: NO Tag: TAG20100908T135312
Piece Name: /u01/oracle/product/10.2.0/db_1/dbs/cf_c-549414289-20100908-00
Control File Included: Ckp SCN: 125665520 Ckp time: 08-SEP-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
56993 Full 11.20M DISK 00:00:00 08-SEP-10
BP Key: 56995 Status: AVAILABLE Compressed: NO Tag: TAG20100908T142547
Piece Name: /u01/oracle/product/10.2.0/db_1/dbs/cf_c-549414289-20100908-01
Control File Included: Ckp SCN: 125668490 Ckp time: 08-SEP-10

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

V10.2.0.5 and Database Target Recovery Catalog Assignments

We recently upgraded to version from version 10.2.0.4 to 10.2.0.5. After, I started to continue where I left off with assigning recovery catalogs to our database targets. What was a simple process previously, is now becoming a headache. First, when adding an already registered recovery catalog I received this message "The specified username does not match the recovery catalog username configured for this database.". I was then told by support to update the back-end repository tables to make the recovery catalog username lowercase. This didn't work so I removed the registered catalog and attempted to add it back. Then I received this message which is rather frightening:
"In this version of Enterprise Manager, recovery catalog settings are now specific to each Enterprise Manager user. Existing recovery catalog settings made prior to upgrading Enterprise Manager have been preserved in order to allow existing backup jobs to continue to work. However, if you change the recovery catalog setting for this database, all non-user-specific settings will be removed, and each Enterprise Manager user that manages this database will have to individually reset their recovery catalog settings for this database. Do you want to continue?"
I can't find any mention of this change in any updated documentation, support page, or other. Essentially, this tells me that as of GC version 10.2.0.5, assignment of a recovery catalog to a given database target is no longer centralized but de-centralized. Each user with OEM GC now has to assign a recovery catalog to each database instance irregardless if their profile is setup as a Super Admin. Or, if you expect to run a manaul backup for a given database you have to log in under a shared account which has all the catalogs assigned which defeats the purpose of any SAS 70 auditing.
I have a ticket in with Oracle support at this time. If anyone has any insight to this I would love to know the reasoning behind it. Thanks.

Well, product development responded with this:
"The catalog management model has been changed in 10.2.0.5GC to
accommodate new database catalog features and enhance security.
Each team member would have to register the catalog separately for the
targets they manage, through their own EM account. This is a one-time
activity. Once that is done, the functionality is the same as before."
What a huge faux pas.

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]

Standby database - RMAN level 0 - Recovery catalog - OEM.

We have configured rman level 0 backup from standby database on OEM. Job is running fine, but rman is not getting connected to recovery catalog. RMAN is connecting to target control file instead of recovery catalog. I understand we need to have DG broker configured for primary and standby for RMAN to connect recovery catalog if you run from OEM. We have configured the DG broker also. DG broker configuration is woriing fine. but Still Standby is not connecting the rman recovery catalog database.
Can anyone tell me what i should check.

Catalog database is same for primary and standby. It is not working for both the version. What are all the basic check i need to do to debug the issue.
THIS IS LOG FROM OEM it is not connecting to target. instead of it is connecting to target control file.
Recovery Manager: Release 11.2.0.3.0 - Production on Thu Sep 6 22:40:28 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
RMAN>
connected to target database: CAAPRD1 (DBID=524360237, not open)
using target database control file instead of recovery catalog
RMAN>
echo set on
RMAN> run {
2> allocate channel oem_backup_disk1 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
3> allocate channel oem_backup_disk2 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
4> allocate channel oem_backup_disk3 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
5> allocate channel oem_backup_disk4 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
6> allocate channel oem_backup_disk5 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
7> allocate channel oem_backup_disk6 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
8> allocate channel oem_backup_disk7 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
9> allocate channel oem_backup_disk8 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAATB1/level0/%U';
10> backup FILESPERSET 1 as BACKUPSET tag 'DAILY_LEVL0_DATA' database;
11> backup FILESPERSET 1 as BACKUPSET tag 'DAILY_LEVL0_ARCH' archivelog all not backed up;
12> release channel oem_backup_disk1;
13> release channel oem_backup_disk2;
14> release channel oem_backup_disk3;
15> release channel oem_backup_disk4;
16> release channel oem_backup_disk5;
17> release channel oem_backup_disk6;
18> release channel oem_backup_disk7;
19> release channel oem_backup_disk8;
20> }

10204 catalog database 112 target database and OEM

catalog database is 10.2.0.4 on server CSERV
OEM server is 10.2.0.4 OSERV
target database is 11.2 on server TSERV
I ran the RMAN command from RSERV (v10204) and registered target database (v112) without error
I went into OEM->TARGET page ->Maintenance->Recovery Catalog Settings->
     selected Use recovery catalog
     (the correct catalog was listed in the drop down (CSERV:1521:RMANUSER-rman_schema1
     added the OS username/password for TSERV
     pressed 'OK'
The error that was returned was:
"Recovery catalog scheme version 10.02 is not compatible with this version of RMAN."
I'm sure i'm doing something stupid, but would really appreciate any help.....
Regards,
Susan

Hi Susan,
Probably you used a 10g rman client on the command line to connect to both the target (11.2) and the catalog (10.2.0.4) during registration.
(according to the compatibilty matrix this works).
Be aware:
When using an older version of the RMAN client with a newer version of the database, you do not get the features of the newer version.According to your own information Grid uses the 11gr2 software.
added the OS username/password for TSERVWhich is incompatible with the 10.2 catalog.
Unfortunately, we can't upgrade the catalog at this time.You can upgrade the catalog schema without upgrading the catalog rdbms (but probably you do not want to execute any change during xmas and new year).
Please check:
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/rcmsynta052.htm
Regards,
Tycho

Rman backup to be stored on other machine than catalog and Target database

I have target database on machine A, catalog on machine B. I am executing RMAN from machine B but want to store RMAN backup on machine C. is it possible.

Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: NEFT (DBID=3608824086)
connected to recovery catalog database
RMAN> run{
2> allocate channel c1 device type disk format '\\bobfs\f\RMAN\data\neft\Rman_NEFT_%U';
3> backup full database;
4> backup current controlfile;
5> }
6>
allocated channel: c1
channel c1: sid=16 devtype=DISK
Starting backup at 15-OCT-08
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00011 name=F:\DATABASE\NEFT\DATABASENEFT_DATA1.DBF
input datafile fno=00015 name=F:\DATABASE\NEFT\UNDOTBS.DBF
input datafile fno=00013 name=F:\DATABASE\NEFT\DATABASENEFT_ARCH_DATA1.DBF
input datafile fno=00002 name=F:\DATABASE\NEFT\UNDOTBS01.DBF
input datafile fno=00001 name=F:\DATABASE\NEFT\SYSTEM01.DBF
input datafile fno=00014 name=F:\DATABASE\NEFT\DATABASENEFT_ARCH_NDX1.DBF
input datafile fno=00005 name=F:\DATABASE\NEFT\EXAMPLE01.DBF
input datafile fno=00012 name=F:\DATABASE\NEFT\DATABASENEFT_NDX1.DBF
input datafile fno=00010 name=F:\DATABASE\NEFT\XDB01.DBF
input datafile fno=00006 name=F:\DATABASE\NEFT\INDX01.DBF
input datafile fno=00009 name=F:\DATABASE\NEFT\USERS01.DBF
input datafile fno=00003 name=F:\DATABASE\NEFT\CWMLITE01.DBF
input datafile fno=00004 name=F:\DATABASE\NEFT\DRSYS01.DBF
input datafile fno=00007 name=F:\DATABASE\NEFT\ODM01.DBF
input datafile fno=00008 name=F:\DATABASE\NEFT\TOOLS01.DBF
channel c1: starting piece 1 at 15-OCT-08
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c1 channel at 10/15/2008 10:45:38
ORA-19504: failed to create file "\\bobfs\f\RMAN\data\neft\Rman_NEFT_7qjt6tat_1_1"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 5) Access is denied.
Recovery Manager complete.
I am executing rman from catalog machine,
WHen i give path \\bobfs\f\RMAN\data\neft\ in start-> run it is accessible from there.
I cant understand why rman is not abl to create file there.
full rights are given to user. and user on rman catalog and network machine is same having same password

Recommendations for recovery catalog database backup

Hi
We are using IBM Tivoli Storage Manager for our 9i db on AIX 5.2.
I would like us to consider using rman but I am not sure of the best way we would go about backing up the database we would use for our recovery catalog.
This database that hold all the metadata would need to be backed up after every rman backup. The rman backup would go to tape, so I am assuming that the recovery catalog would be backed up on tape also.
What are the common procedures for this in other shops ?

Dan A wrote:
Aman. That doc does help, and indeed it does explain
Back up the recovery catalog with the same frequency that you back up the target database.
We would be doing nightly backups, so we would have to back up the catalog with the same frequency.
The doc explains that we would use rman for these backups also, but that it would be in NOCATALOG mode so that the repository is in the control file.
And then what? Just copy this to tape? Seems that with rman there is then a need to do two backups - one of the target db and one of the recovery catalog.
Thanks.I shall suggest to take an export of the underlying schema which is holding the info in the recovery catalog. That's all which is basically required to be safe. In case , everything gets burnt regarding the catalog db,you can immediately create another db, import the user back there and things are in place. This should be a quick and easy way out of the backup of recovery catalog.
Yes if you are going to take backups every night than backup of recovery catalog schema/db nightly will be a good option. Docs are meant to promote people for RMAN so indeed they would talk about it. But its not at all a compulstion to use RMAN for recovery catalog schema's backup. If its a big catalog maintaining lots of database's info than using RMAN with all its features is a good option. If a single db is a part of it than it may not be that much big and export of teh schema alone may serve the purpose too.
HTH
Aman....

How to un-register target database in Catalog DB?

I am using 8.0.5. I create a Catalog database and register a target database with it for online backup. How do I un-register a target database from the Catalog DB if I do not want to continue taking backup? Is there any 'unregister' command?
Thanks in advance
- Sanchayan RoyChoudhury
Bangalore, India
null

Let me try...
If u know your dbid (which can be found out by just logging into rman with the target databasse)
login ot the catalog database throught sqlpplus as the catalog schema owner...
run the following query..
SELECT db_key, db_id FROM db WHERE db_id ="dbid just found";
then run
execute dbms_rcvcat.unregisterdatabase(db_key, db_id);
This will unregister your database from the catalog. however keep in mind that you will lose all records of your old backups..
HTH
null

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

Views to check the catalog database name from target database.

Hi,
Please help me to find view to check the catalog database name which is connected to my target database because I am new to the current environment where I am working now and the previous DBA have done the set up having 2 catalog database. I want view to check from target database, which can show the catalog database name to which it is connected to.
We can check the catalog database name from the following ways but I want views to check it from target database.
1.TNSnames.ora
2.Any backup script connecting to catalog database.
3.From catalog database we can use rc_database view to check the databases registered with the catalog database.

Please help me to find view to check the catalog database name which is connected to my target databaseYou can check for any RMAN backup jobs that been scheduled on the server.
In the scheduled script check rman command.
You can then identify the database alias (of the catalog db) that is used in the rman backup script.
Once you have found the database alias, check for the database alias entry in tnsnames.ora file present in your target database server.
Once the entry is found, you can find the IP address and catalog db name from the tns entry.
Edited by: st. osh on Nov 22, 2012 11:38 PM

Oracle RMAN recovery catalog database in a Primary and Standby mode

Hello All,
The customer wants the RMAN recovery catalog database to be highly available so that none of the RMAN database backup jobs are impacted at the time of taking the database backups. There are are 200+ databases running on OEL, RHEL and Windows. So we planned to host the recovery catalog database on Oracle Active DataGuard 11.2.0.1 Enterprise Edition on RedHat EL 5.8 version on two physical servers. The Primary Instance will be in one server in the Primary DC and the Standby Instance will be on another server in another DC. Also all the database datafiles are hosted in ASM Diskgroups on SAN (DATA, FRA, REDO, ARCH diskgroups).
Are there any specific RPM/patch/OS user custom/specific settings or configurations needed..?
Thanks in advance..
Regards,
Abhijit

"The customer wants the RMAN recovery catalog database to be highly available so that none of the RMAN database backup jobs are impacted at the time of taking the database backups"
Hi,
i think you can achieve HA for the catalog DB. (Rac and Asm should work fine)
There's no way (afaik) to use TAF with the rman backup. If you have a failure during a backup it simply fails.
There is no TAF in this situation.
Hope this helps.
Regs,
Drew

Recovery catalog, target database.

Similar Messages

Maybe you are looking for