RE: switch logfile vs. archive log current

I use switch logfile exclusively within my hot backups (because at the time I wrote the scripts I was unaware of the difference) but also check V$LOG to make sure the archive write is complete before proceeding with the backup. I has worked fine on my 8.x production database for the last 4+ years (including daily recoveries to build a Reporting instance).

I do have a question though. What is the purpose of switching the logfile for each tablespace? I do it once, after all of the tablespaces have been backed up. Am I missing something?

Mike Hand
Polaroid Corp.

-----Original Message-----
From: Hemant K Chitale [mailto:hkchital_at_singnet.com.sg] Sent: Wednesday, March 19, 2003 11:49 AM To: Multiple recipients of list ORACLE-L Subject: Re: switch logfile vs. archive log current

A "switch logfile" isn't mandatory and an "archive log current" is highly recommended.
The "switch logfile" command would return immdiately and would not wait for the archiver to complete archiving the log. The "archive log current"
would return only after the archiver has completed it's job. You must backup the archivelogs from the first one generated after the first "alter tablespace begin backup" to the first one after the last "alter tablespace end backup". You are also backing up the controlfile which is also highly recommended.

I normally use a combination of multiple "switch logfile", "archive log" commands and
a Unix "sleep" command and then exclude the last archivelog from the backup Received on Wed Mar 19 2003 - 12:27:48 CST