On Tue, 2 Oct 2001, Ron Rogers wrote: > Some reasons why NOT to put all tablespaces in the backup mode at > once (step 1) is that the tranactions against the database could > create a lot of redo and archive logs that could fill the space, > tranaction time could be longer as it now reads the redo not the > tables
What reads the redo? I don't think you have to read the redo during hot backup mode. You read the datafiles or buffer cache just like when you're not in backup mode. > Snapshot to old could occur Why? I can think of no reason that ORA-1555 should be more likely during hot backup mode. Can you explain this? > If there is a problem and the server restarts Oracle will not start > tablespaces in the backup mode you have to manually issue the > "tablespace normal" command. Do you mean 'alter database datafile <n> end backup?' This can and should just be integrated into the database start scripts. -- Jeremiah Wilton http://www.speakeasy.net/~jwilton -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jeremiah Wilton INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- 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).
