Re: rman catalog and current controlfile

Goran,
i think the catalog is serving its purpose well in this scenario. since backup info is written to the catalog only at backup time. the node that the backup is having on in you case the standby's controlfile will only have this info. i had not read of any way to add the information back to the control file of the primary node so to say. resync controlfile is an interesting command according to the documentation You can also use RESYNC CONTROLFILE to resynchronize the current control file with the RMAN repository in a control file copy. Why would this not be the command you want ot use in this case. it does solve the purpose and intent i guess. thanks for letting me know about this command though. ----- Original Message ----
From: goran bogdanovic <goran00_at_gmail.com> To: oracle_l <oracle-l_at_freelists.org>
Sent: Wednesday, July 18, 2007 4:07:31 AM Subject: rman catalog and current controlfile

Hi all,

I have configuration of one primary and one physical standby. the backups are done on standby and recovery catalog is in use. if I connect using rman on primary and catalog, primary is 'aware' of all backups done on standby. If I connect (rman) with no catalog, primary do not 'see' backups done on standby. I have tried to find a way (except cataloging backups on primary) to 'refresh' records in primary controlfile from catalog. In documentation "Backup and Recovery Reference 10R2' is mentioned command: RESYNC CONTROLFILE which says:
<>

The primary use for RESYNC CONTROLFILE occurs when you re-create the control file (for example, to change the database name), which causes you to lose RMAN records. You can then resynchronize the newly created control file with an old copy.
<>

which is not appropriate in this case.

Does anybody know some method of 'refreshing' the backup info in controlfile from recovery catalog?

Thanks.
Goran

--
http://www.freelists.org/webpage/oracle-l