Re: rman catalog and current controlfile

From: goran bogdanovic <goran00_at_gmail.com>
Date: Wed, 18 Jul 2007 13:27:09 +0200
Message-ID: <6d0a3ba80707180427n5ddbde37yee1d2ccbb1957b8c@mail.gmail.com>

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 10.2.0.2
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

Thanks.
Goran

On 7/18/07, Fuad Arshad <fuadar_at_yahoo.com> 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 Element* *Description*
>
> CATALOG
>
> Updates the recovery recovery catalog with RMAN metadata in the current
> control file (default) or a control file copy.
>
> CONTROLFILE
>
> Updates 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).
>
>
> ----- 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

Received on Wed Jul 18 2007 - 06:27:09 CDT