Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> Re: rman catalog and current controlfile

Re: rman catalog and current controlfile

From: Fuad Arshad <>
Date: Wed, 18 Jul 2007 06:18:42 -0700 (PDT)
Message-ID: <>

ok look like you are right the command syntax looks like

resync catalog from backup controlfile '/tmp/backup_01.ctl'; or
 resync catalog from controlfilecopy '/tmp/backup_01.ctl';  this means that in case of catalog loss you can use a copy of the controlfile that you can keep on disk .(We do regular binary controlfile copies justi n case) and create a new catalog and resync it.

Hi Fuad,

the usage of catalog is fine as long as recovery catalog is 'there' and available. In case that catalog is complitly lost (can not be recovered) the current control file is missing information about backups. One option is to catalog backups in current CF, the second which I was thinking of to do (on regular basis) sync. of current CF from information found in rec. catalog. The command RESYNC CONTROLFILE I forgot to mention in OP does not work :-) at least at RMAN recognize only RESYNC CATALOG.

RMAN> resync controlfile from

RMAN-00571: =========================================================== 
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "controlfile": expecting one of: "catalog" RMAN-01007: at line 1 column 8 file: standard input


On 7/18/07, Fuad Arshad <> wrote: another addition you can also make a controlfilecopy from the standby node and use that to sync the primary per the syntax below. Syntax ElementDescription
CATALOGUpdates the recovery recovery catalog with RMAN metadata in the current control file (default) or a control file copy. CONTROLFILEUpdates the current control file (and recovery catalog, if RMAN is connected to one) with RMAN metadata from a control file copy. FROM CONTROLFILECOPY 'filename'Specifies the name of the control file copy to use for resynchronization. Physical schema information is not updated when you use this option. Note: The control file copy can either be in the current database incarnation, or created in a prior incarnation (that is, prior to the most recent OPEN RESETLOGS).

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?


Received on Wed Jul 18 2007 - 08:18:42 CDT

Original text of this message