Technically, after a consistent shutdown, the redo logs are not needed. All transactions have been completed thus no redo is necessary.
However, I consider a full backup to include redo logs and control files. The issue is not whether the database needs them for recovery, but whether the dba needs them to speed recovery. A full restore of database from cold backup is required. Yes, the online logs are not needed and can be recreated from scratch. However, there is less human intervention and thus less room for error if all the files are restored from tape (or other) and the database opened. Just these two steps are required. For any backup, you should never backup an active redo log. This is one where redo is being written. If you are doing cold backups, the database is not writing redo, so there are no active logs. If you are doing hot backups, you will need to get all of the redo from archived logs that covers the time period from just before the first tablespace was placed in backup mode to just after the last tablespace was taken out of backup mode. Consider the small size of most redo logs compared with the possibility of loss and I'll back them up every time. Dan -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Fink, Dan INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
