Usenet.com

www.Usenet.com

Group Index

Comp Thread Archive from Usenet.com

<-- __Chronological__ --> <-- __Thread__ -->

benefits of multiple switch logfile calls?



Testing hot backup strategy for Oracle 9.2.0.4.  Due to space concerns I'm
not using RMAN right now, just putting tablespaces in backup mode and
gzipping datafiles to backup dir, similar to what we do now in Oracle
7.3.4.5.

One problem I have is that my test recover failed complaining that it
needed to apply more archive logs.  The logfile it asks for was not
created.  In my new backup script I call "ALTER DATABASE ARCHIVE LOG
CURRENT" before copying over the log files.

However in the Oracle 7.3.4.5 (written by wiser consultant 5 years before
my time) script, there are three "switch logfile" statements in succession
followed by the archive log current, literally like this:

  ALTER SYSTEM SWITCH LOGFILE;
  ALTER SYSTEM SWITCH LOGFILE;
  ALTER SYSTEM SWITCH LOGFILE;
  ALTER SYSTEM ARCHIVE LOG CURRENT;

Would that fact that I'm not calling SWITCH LOGFILE at all (let alone
multiple times) lead to the fact that I'm missing some redo info?  I don't
understand why multiple calls are of any value, but I've seen it done in
other scripts on the web and in the Oracle news groups.



<-- __Chronological__ --> <-- __Thread__ -->


Usenet.com



Please check out one of the premium Usenet Newsgroup Service Providers below for access to Usenet.