Re: Controlfile confusion

From: Alex Fatkulin <>
Date: Thu, 15 Jan 2009 22:13:23 -0500
Message-ID: <>

  1. Snapshot controlfile is not a backup. It is used by RMAN to get a consistent copy of a primary controlfile to work with (because otherwise it would require a long-term locking of the primary controlfile).
  2. See above
  3. It can be used to rebuilt the controlfile from scratch and paired with RMAN's catalog command can be populated with all required metadata about your backups. It can save you the troubles of typing the entire thing yourself if you desire to do so one day.

On Thu, Jan 15, 2009 at 9:58 PM, J. Dex <> wrote:
> I inherited a script that runs an rman nocatalog cold backup in a
> database. There appears to be 3 different copies of the controlfile that
> get generated. In the event of a restore, will there be an issue if any of
> them are missing? Which one would the restore use? Here is the scenario:
> 1. In the rman configuration, 'CONFIGURE SNAPSHOT CONTROLFILE NAME TO
> ..'is left at default so a copy of the controlfile goes to the
> $ORACLE_HOME/dbs directory.
> In looking at the log, there is also an autobackup of the controlfile that
> goes to the flashback_recovery_dest which is determined by the database
> setting (which is a different directory than the backup directory mount
> point that the backup piece itself is actually going to). Shouldn't
> flashback_recovery_dest be set to the same directory as the backup itself?
> If there were a restore and the file in the flashback_recovery_dest is not
> there, but still have the one that is located in the /dbs directory, will
> there be any issues?
> 3. After the database is restarted and opened, the script does an alter
> database backup controlfile to trace. Is this 3rd backup controlfile even
> worth anything since it is run after the database is re-opened?
> ________________________________
> Windows Live™: Keep your life in sync. Check it out.

Alex Fatkulin,
Received on Thu Jan 15 2009 - 21:13:23 CST

Original text of this message