Register in catalog

Hi,
When i connect to the RMAN catalog database and do:
RMAN> report schema; --am getting..
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 03/04/2006 21:17:21
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20003: target database incarnation not found in recovery catalog
--But when i try to register database...
RMAN> REGISTER DATABASE;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 03/04/2006 21:13:32
RMAN-20002: target database already registered in recovery catalog
--can anyone tell me what the problem could be?

Perhaps this database is a copy of another. ie the dbids are the same.
please refer to Metalink note 1013368.102 for more information

Similar Messages

Registering recovery catalog in Enterprise Manager

Hi,
I created recovery catalog database successfully using RMAN of 10g R2 on command prompt. Every thing seems working fine on RMAN but when I connect to target database using EM and click the recovery catalog link, it does not show me the configured recovery catalog. When I try to configure the catalog, it gives me the error message "Bad Packet". I dont what the problem is. Can any one help me with this?

Hi,
I am using winXP and using EM DB of Oracle 10g. I used RMAN on command prompt and created recovery catalog by creating a recovery catalog user and assigning a catalog user to it. I have also registered target database with recovery catalog. Now all this is working on command prompt using RMAN utility. Both target and recovery are on one computer. Now when I try to see recovery catalog in EM DB, its says no recovery catalog has been configured and when I try to configure recovery catalog, following error message keeps coming
Validation Error
Examine and correct the following errors, then retry the operation:
Error - java.sql.SQLException: Io exception: Bad packet type
*Host--------- shahnawaz
* Port---------5500
* SID-----------qasimdb
* Recovery Catalog Username-----zee
* Recovery Catalog Password------zee
I hope my question is quite clear. If you need more info. just let me know please. I will appreciate.
regards,
Qasim

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] [] [] [] []

Unable to register database in catalog into emrep

Hello guys,
I have a RMAN catalog in one server that works fine, now I tried to move this catalog to the emrep database (In this database I have the Grid Control), as I can´t use export / import because the original database is 10.1.0.5 and the emrep database is 10.1.0.4, I have created a new catalog into the emrep database.
The problem appear when I try to register one database on it:
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 09/15/2009 12:10:43
RMAN-10015: error compiling PL/SQL program
RMAN-10033: error during compilation of job step 1: ORA-01041: internal error. hostdef extension doesn't exist
ORA-04029: error ORA-3113 occurred when querying ORA_KGLR7_DEPENDENCIES
So, my first question is: Is possible create a RMAN catalog in the same database of Grid Control?
If this is possible, any suggestions that can help me to resolve this errors?
Thanks.

Hello Damorgan, thanks for your answer.
I follow the steps in a remote database ( BEEVODES ) which I want register into catalog ( tstsuse11-emrep ):
oracle@srvdb01 ~]$ echo $ORACLE_BASE
*/u01/app/oracle*
oracle@srvdb01 ~]$ echo $ORACLE_HOME
*/u01/app/oracle/product/10.1.0/db_1*
oracle@srvdb01 ~]$ export ORACLE_SID=BEEVODES
oracle@srvdb01 ~]$ rman target / catalog rman@tstsuse11-emrep
Recovery Manager: Release 10.1.0.5.0 - 64bit Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: BEEVODES (DBID=822996874)
recovery catalog database Password:
connected to recovery catalog database
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 09/16/2009 12:12:49
RMAN-10015: error compiling PL/SQL program
RMAN-10033: error during compilation of job step 1: ORA-01041: internal error. hostdef extension doesn't exist
ORA-04029: error ORA-3113 occurred when querying ORA_KGLR7_DEPENDENCIES
But I continue with the same error.
I supose the instalation of emrep is ok, because the Grid Control ( installed there ) works fine.
Thanks again.

Registering primary database to catalog database.

Hi all,
Here we have a 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?

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] [] [] [] []

Our RMAN Catalog Problem

Hello
We have 7 major oracle instances on 2 servers and we have created a RMAN catalog on another server
Our principal databases are Standard Oracle 10g (10.2.0.2.0) under linux , and the catalog is Enterprise Oracle 10g (10.2.0.2.0) in Windows all the databases are registered in catalog when I query RC_DATABSE view it shows all
instances informations , in all RMAN login commands the "CATALOG" clause has been written
Now my problem is that just two of databases backups are recorded in catalog for example when I query "RC_BACKUP_SET" view it only contains backups of two databases while are backups have been performed completely without any error
Do you know what is problem ?
thank you

select dbid,name from rman_user.rc_database;
DBID        NAME
<h4>----------------  ----------------</h4>
1498968931       SCSDB
4293064263        SSTDB
861276728         SUBDB
2404423160        SAM
3976246282        SFIDB
1760672514    SCEDB
817528985        S900NS1
select t.name,t1.db_id,bs_key
from rman_user.RC_BACKUP_SET t1,rman_user.rc_database t
where t1.db_id=t.dbid;
NAME        DB_ID        BS_KEY
<h4>----------------  ----------------  ----------------</h4>
SUBDB        861276728        14366
SUBDB        861276728        14365
SUBDB        861276728        14364
SAM        2404423160        14491
SAM        2404423160        14490
SAM        2404423160       14489
select name, max(START_TIME)
from rman_user.rc_database d,
rman_user.rc_backup_set s
where db_id(+) = dbid
group by name
order by 2 desc;
NAME        MAX(START_TIME)
<h4>----------------  ----------------</h4>
SCEDB
S900NS1
SCSDB
SFIDB
SSTDB
SAM        6/14/2008 1:06:15 AM
SUBDB        6/13/2008 9:02:43 PM
This date (6/14/2008) is old because I haven't used the catalog for a long time, due to the problem I've mentioned above.
Edited by: TakhteJamshid on Jan 10, 2010 2:49 AM
Edited by: TakhteJamshid on Jan 10, 2010 3:00 AM

RMAN catalog/controlfile

Gurus ,
please clarify me below things
thanks for great help .. .
1) can rman backup information will be stored in both controlfile and catalog db at a time ? ( if target db is registered in catalog db)
2) how to know if db is only using controlfile for storing rman backup operations.
3) how to check if database is configured to use catalog db for rman operations ?
4) rman backup database plus archivelog;
will this command backups only archivelogs after start of backup operation (or) backup older files also which exists in archive destination.
Thanks
raj

1. RMAN Backup information is always written to the controlfile. If you are using a catalog, it will be written to the catalog in addition to the controlfile --- i.e. to both locations. However, retention of information in the controlfile is generally subject to the lower of controlfile_record_keep_time or the number of slots available in the controlfile while retention of information in the catalog can be and is generally much larger.
2. You can't know, from the database itself, whether it is writing to catalog schema or not. You can query the database's V$ views for information that is in the controlfile.
3. The database doesn't store information about whether a catalog is being used or not -- it doesn't know. You have to connect to the catalog to query for information about the target database's backups.
Remember : When you start RMAN, you must explicitly provide the CATALOG location (username/password@catalog_instance) otherwise, the default is NOCATALOG.
4. BACKUP DATABASE PLUS ARCHIVELOG will also backup Archivelogs that are present and were generated before the database backup began.
Hemant K Chitale

Pecification does not match any archive log in the recovery catalog

MAN> list archivelog all;
pecification does not match any archive log in the recovery catalog
RMAN> list backup of archivelog all
BS Key Size Device Type Elapsed Time Completion Time
671197 5.17M DISK 00:00:03 29-MAY-11
BP Key: 671200 Status: AVAILABLE Compressed: YES Tag: TAG20110529T180030
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_FVMDIGPU_S25087_P1
List of Archived Logs in backup set 671197
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44836 503663671 29-MAY-11 503675934 29-MAY-11
2 22517 503663669 29-MAY-11 503675932 29-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671232 5.12M DISK 00:00:02 29-MAY-11
BP Key: 671235 Status: AVAILABLE Compressed: YES Tag: TAG20110529T200050
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G1MDINRJ_S25089_P1
List of Archived Logs in backup set 671232
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44837 503675934 29-MAY-11 503688661 29-MAY-11
2 22518 503675932 29-MAY-11 503688659 29-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671267 5.14M DISK 00:00:03 29-MAY-11
BP Key: 671270 Status: AVAILABLE Compressed: YES Tag: TAG20110529T220036
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G3MDIUS4_S25091_P1
List of Archived Logs in backup set 671267
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44838 503688661 29-MAY-11 503701009 29-MAY-11
2 22519 503688659 29-MAY-11 503701007 29-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671302 16.55M DISK 00:00:05 30-MAY-11
BP Key: 671305 Status: AVAILABLE Compressed: YES Tag: TAG20110530T000048
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110530_G5MDJ5TG_S25093_P1
List of Archived Logs in backup set 671302
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44839 503701009 29-MAY-11 503716961 30-MAY-11
2 22520 503701007 29-MAY-11 503716959 30-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671337 5.13M DISK 00:00:02 30-MAY-11
BP Key: 671340 Status: AVAILABLE Compressed: YES Tag: TAG20110530T020121
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110530_G7MDJCVI_S25095_P1
List of Archived Logs in backup set 671337
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44840 503716961 30-MAY-11 503729544 30-MAY-11
2 22521 503716959 30-MAY-11 503729542 30-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671372 5.25M DISK 00:00:03 30-MAY-11
BP Key: 671375 Status: AVAILABLE Compressed: YES Tag: TAG20110530T040055
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110530_G9MDJJVN_S25097_P1
the archives are in the location of
F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G1MDINRJ_S25089_P1
when it is not specified in catalog how can i delete archives from f location i.e
F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G1MDINRJ_S25089_P1
please let me know from rman how can i delete archives from f location...........................
do i need to register with catalog?
i have used Delete archivelog all completed before 'SYSDATE-10';
but no use
out put is
MAN> Delete archivelog all completed before 'SYSDATE-10';
eleased channel: ORA_DISK_1
llocated channel: ORA_DISK_1
hannel ORA_DISK_1: sid=311 devtype=DISK
pecification does not match any archive log in the recovery catalog
MAN> crosscheck backup archivelog all;
please send me the query which i can delete ......................thanks
cheers
mahesh

EdStevens wrote:
856483 wrote:
<snip>
can i have you mobile contact phone number if possible?
I have seen some pretty astonishing requests on this board, but this one really raises (or lowers) the bar. Just what is it your boss is paying you to do?
Some listserves have lots of people giving their number. I find it odd that people would, but not astonishing for someone to ask. Outside the norm here, but how would someone know ahead of time? It's a bravely connected new world.

Reg Target connection failed from catalog

Hi,
i am configuring RMAN in my PROD.
I have seperate catalog database.
I have added the TNS Entry of both in PROD and CATALOG Server.
TNSPING from both server is working.
I have created the password file in PROD.
When i issue the command
rman catalog rman/rman target sys/sys@PROD it gives below error.
RMAN-04005: error from target database:
ORA-01017: invalid username/password; logon denied
But when i give
sqlplus sys/sys@PROD
it is getting connected.
One more thing already a test database is registered in the catalog as target.
Is there any Restriction that only one target can be registered in catalog.
If so how to deregister the existing target database.
Kindly help in this regard.
Regards
Krishna

refer the link: i already mentioned:
Whether if i register the database using the second scenario then if try to connect using first ,will it work?you can connect with any database from rman, but why? no need, you can directly connect with recovery catalog from target.
you can get the backup information only from registered recovery catalog database.
IF i deregister the existing target database say TEST will the backup list of TEST will be removed automatically.yes, all information from recovery catalog is removed.
why you get confusion, register a database with recovery catalog is very simple
1. create a recovery catalog user and grant recovery catalog owner role to user.
2. connect the target database with the recovery catalog database
3. register the database with the recovery catalog database.
4. connect as recovery catalog datbase user and verify it using rc_database recovery catalog view.
refer the link i already mentioned.
else:
http://arjudba.blogspot.com/2008/05/how-to-create-recovery-catalog-and-use.html
Edited by: rajeysh on Jul 14, 2010 11:47 AM

Big Difference between Catalog and Nocatalog

Hi,
i´m always facing the discussion, what is the big difference between using a catalog and nocatalog
i start with the points i know. could somebody please add some points? Thanks
(+) Catalog
1. All Controlfiles could be lost (but if you have controlfile autobackup it should not be a great problem without the catalog)
2. keep forever backup (controlfiles yould only save information up to 365 days)
3. many database backups could be administrated inside the catalog (but what if yoiu want to know: which of my 100 databases are not backed up yesterday?)
4. ....?
(-) i had some crash scenarios that worked only without catalog
(-) backup of the catalog
(-) another database on another server
Thanks
Marco

Hi,
Using catalog you have the advantage to keep global RMAN script. Those scripts can be run against any of the databases registered in the catalog.
You can use following command to see the script if already written and stored in catalog:
RMAN > print script "local_script_name.rcv" ; [specific to your database and would run against your database]
RMAN > print global script "script_name.rcv"; [global script which can run on all the database registered with catalog]
Thanks
Sumit.

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.

How do I tell if the RMAN Registration has worked correctly?

Am using Oracle, DataProtector and SAP with RMAN and am registering the database in RMAN using the standard DataProtector commands.
How do I tell that the database has actually registered the catalog inside the RMAN DB? I can do a "list backups" but it does not tell me whether the control file is being used for the catalog or the RMAN Database. Can anyone assist?
Share and Enjoy! Ian

I believe I have registered the database to use the
RMAN Database to store the catalog - how do I confirm
this?issue some rman commands which access the recovery catalog like 'list backup' or ask the recovery catalog:
'select * from rc_database'
regards,
-ap

RMAN in DataGuard Technology

Hi,
our Business requirement is:
1-having Full backup on Sat on produciton side and incremental backup every day.
2- Having Full backup on Sun on Standby database and incremental backup every day.
to fulfill these requirement i did the following:
1- inremental backup 0 on prod on Sat and Differential incremental backup 1 every day and store in directory called /prod/
2- Incrementally Updated Backups starting On Sun on the standby side and run every day, and store in directory called /standby/
I read the documentiaiton and it says the best practice is doing the following:
having Catalog database==> done.
having unique database name on prod and each standby DB==> done.
do Incrementally Updated Backups on standby side to minimze the performance in the prod side ==> done.
take control backup and spfile on the prod db==> done
i followed those essential best practice from Oracle documentation and i just add one thing which is taking the backup alos in the prod side.
now when i run list backup command from RMAN session and i can see the backup in both servers prod and standby, and if i lunched from prod server, i can see the backup that taking in both servers registered in catalog, however for standby db the status is expired which is makes sence because those backup files phyisical not excite in the prod server and the same thing happen if i lunched the rman from standby server, i found the backup of prod is expired.
Now My questions:
1-How can i force catalog to distingusih between those 2 backup and doesnt give me expired status?
2- i set up the retention policy for 7 windows day, it works fine for the stanby database and delete those files that > 7 but in prod doesnt work, looks like couldnot solvo the retention policy and i guess because i am taking full backup 0 on Sat and this against the Incrementally Updated Backups that takes on Sun, How can i solve this one?
3- i did restore senario for the backups i am taking on test server and the result was for the Incrementally Updated Backups that took on standby, i was able to restore and recover to the point i want and it works like the way it should be, but when i did another restore senario with the backup from prod server, didnt work, it restore the full backup 0 and then didnt apply the incremetail backup i have from the following day, however it asks for applying archives log instead of using the incremental backup, i though RMAN smart enough to choose between restore from incremental or from archives. How can i restore with DB with the backup i have from prod? btw, when i did the restore senario on test, i didnt connect to catalog though, i only connect to targer in both senarios
rman targe /
RMAN >.......
4- Should i stop taking backup on prod side and stay enough with the Oracle recommendation by taking only Incrementally Updated Backups on standby DB?
THE PARAMETER SETTING IS
on the prod side:
oracle:XXX:/export/home/oracle # rman target / catalog rman/rman@catalog
Recovery Manager: Release 10.1.0.5.0 - 64bit Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: XXX (DBID=1665948166)
connected to recovery catalog database
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/app/oracle/10.1.0/dbs/napcf_XXX.f'; # default
RMAN> exit
Recovery Manager complete.
Finally MY OS is linux
DB is 10.1.5
I am sorry for long thread but i want to be clear as possible and I can and Thanks for the help and suggestion.

Firstable, thanks God that some1 finally answer the question.
All your points are correct and that is what i followed exactly, and if you read my thread you will notice that i did follow the practice correctly, however, as i mentions it is business requirement that ask to have 2 back up on prod as well as on standby ( and the backup on prod is extra step as i said in my thread , i know it is not part of the best practice ), for me as DBA i agree with only one backup in standby DBs, but again this is business requirement not my decision.
The key concept is there is 1 database, and only 1 backup is required, either primary or standby, not both.
this is not really true,
check this pdf file from Oracle on Appendix A, http://www.oracle.com/technology/deploy/availability/pdf/RMAN_DataGuard_10g_wp.pdf
you will find it is possible to have backup on primary as well as standby, but my only problem is with the Catalog how can i enforce them to recoginze those backups especially when i lunched the delete commands, i need to delete file that not satisfy my retention policy, due to the fact that there are 2 full backup happen in different time on Sat in prod server and on Sun standby , looks like the catalog couldnt solve this issue, therefore when crosscheck and delete command issue couldnot delete the backup that more than 7 days.

RMAN-target database not found

Hello All:
we have rman config (0 level bkp) for our PROD backup, rman catalog is on a different server. running OK. heaving 0 level backup of our PROD.... no issue.
Now we have one more PROD db implemented recently for payroll on seperate server, so we decided to have rman backup of this also.
we set that rman script to here also and made the neccessary changes.
It is heaving backup, archive backup ... no issue ...
but it error while "RMAN Catalog resync"
that part from script is
## RMAN Catalog resync ##
rman log=/u01/bkp/logs/backup_resync.log << EOF
connect catalog rman/rman@rman
connect target /
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/bkp/backup/ctrl_%F';
resync catalog;
EOF
and the error on log file "backup_resync.log" getting:
Recovery Manager: Release 11.1.0.6.0 - Production on Fri Aug 10 04:25:04 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: ORCL (DBID=2588904899)
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 08/10/2012 04:25:29
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog
RMAN>
Recovery Manager complete.
plese suggest on this, i googled, saying to register the catalog, tried but no luck....
thanks in ADV
Edited by: DOA on 9 Aug, 2012 10:16 PM
Edited by: DOA on 9 Aug, 2012 10:17 PM

Hello vreddy,
Thanks for the reply...
I am bit new with the rman word....
I tried command on server where catalog exist (stating: my PROD and catalog exist on different different server)
(orcl is my PROD db name)
rman target / catalog ORCL
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Aug 10 10:57:29 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: RMAN (DBID=1583459273)
recovery catalog database Password:
asking for some password, which password here we need to supply ?
for more clear picture I also execute command on catalog side:
SQL> select name,DBID,RESETLOGS_TIME from rc_database order by 1;
NAME DBID RESETLOGS
PROD 4247251480 12-MAY-04
RMAN 1583455429 02-JAN-09
db ORCL is not there in the list....

Physical standby using rman

Step By Step Guide To Create Physical Standby Database Using RMAN
Doc ID: Note:469493.1
says: Step 2: Move the backups to the standby server
I'm a rman novice. What does that move look like? Do I copy the various files mentioned in the backup output, like /u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_annnn_TAG20071209T145731_3oqf84xl_.bkp or is there some other glue that has to be performed to make the standby system see the backup correctly.
Could I just tar up the FRA?

Hi,
You can place your backup whatever you find it appropriate and catalog it on the target server using catalog rman command.
Your FRA can be large and it can take time to copy all content of FRA to target server.
The best way to use backup ... format '<path_to_backup location>/bkp_%U'; Then copy backup piece(s) to target server and register with catalog start with '<path_to_backup location on target server';
Best Regards,
Alex

Register in catalog

Similar Messages

Maybe you are looking for