Re: benefits of multiple switch logfile calls?

On Fri, 05 Dec 2003 06:46:13 +1100, Howard J. Rogers wrote:
> It also explains why the original poster complains about the recovery
> process using redo from a time after the backup completed: because the
> restored controlfile has no idea when to stop recovering, because it is
> itself out of date.

That's me! I realize that ignorance is no excuse but when I came onto this job that is how I was told to do the copies. My revised orahot script (mostly found online here) does backup the control file to trace, and has these instructions:

#  If you need to clone the entire database, load the *exact same* Oracle
#  software binary image, restore the contents of the backup, then edit the
#  file named "ora*.trc". Remove everything except for the "CREATE CONTROLFILE",
#  modify the paths if necessary, then enter svrmgrl (or sqlplus on 8i+),
#  do a "startup nomount", then run the "CREATE CONTROLFILE". After a delay,
#  do a "RECOVER AUTOMATIC DATABASE;" and after another delay, enter
#  'ALTER DATABASE OPEN;' and your database should come online. Also make
#  sure that you've renamed the "do-not-use*" redologs to working paths.

That last sentence refers to the fact that it copies the redo log files (as listed in v$logfile) and prepends "do-not-use-" to the copied files.

I realize this question warrants an "RTFM", but are these pretty solid instructions. I'll probably try to train myself to do things the right way instead of the way the DBA-on-the-way-out-the-door told me.

Also, Howard, you think that just the ALTER SYSTEM ARCHIVE LOG CURRENT; statement is enough? Does it matter if we do it before or after backing up the control file to trace? Received on Thu Dec 04 2003 - 14:00:24 CST