And of course remember to make a copy of the online logs before you begin recovery, so that if anything goes wrong you can try again. (note this is *not* a contradiction of the wisdom of excluding the online logs from "hot" backups. Backing of the online logs is a step of recovery (the first if you agree with me), *not* a part of the backup process (since it is far too easy for operations to reload them over the top of the online logs you need.) mwf -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Ruth Gramolini Sent: Tuesday, June 15, 2004 11:46 AM To: oracle-l@xxxxxxxxxxxxx Subject: RE: recover database question See answers inline: Note, you can set an until time inconjunction with the until cancel. HTH, Ruth -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Jos Sent: Tuesday, June 15, 2004 8:35 AM To: oracle-l@xxxxxxxxxxxxx Subject: recover database question List, What the difference in doing the following two: recover database using backup controlfile until cancel This will only be possible if you don't need any archivelogs to have the database consistant. If what you need is still in the redo logs than you can cancel the recovery and it will be ok. and recover database using backup controlfile => Oracle prompt for archive log type CANCEL once all archivelogs are done. This will work if you have all of the archivelogs needed ir can restore them from backupsets. When you have applied all archived logs and there is only a redo log left, you can cancel. You will get a message if you can't do either operation which will let you know that you won't have a consistant recovery and an open resetlogs will fail. Regards, Jos ---------------------------------------------------------------------------- -- Find local movie times and trailers on Yahoo! Movies.