Frankly,
David, (and possibly embarrasingly) I am not an RMAN aficionado. I do backup and recovery the "Old Fashioned Way"...manually. Well, kind of...I actually have written my own scripts that I have used successfully for years to do what RMAN does, therefore, please forgive my ignorance of RMAN.
If you do not use the RMAN command, "RECOVER DATABASE", to recover your database, guess what the non-RMAN command is to recover your database...it's "RECOVER DATABASE".
Secondly, the command to recover a database to a specific point in time is:
Code:
RECOVER DATABASE UNTIL = 'MM/DD/YYYY HH24:MI';
Thirdly, the redo logs play a role in the RECOVER process, but if you are doing a full database restore, then your must also restore your on-line redo log files since they are one of the three vital groups of files in an Oracle database (i.e., Database Datafiles, On-line Redo Log Files, and Control Files).
If your database failure occurred more recently than your oldest on-line redo log file, then the RECOVER command uses data only from your on-line redo log files. If your failure occurred prior to your earliest on-line redo log file's oldest entry, then RECOVER
must use archived redo log files
and on-line redo log files (since the most recently COMMITed transaction has not been archived and resides only in your current on-line redo log file.
Does this filter out some of the mud? BTW, your questions are excellent.
![[santa] [santa] [santa]](/data/assets/smilies/santa.gif)
Mufasa
(aka Dave of Sandy, Utah, USA)
[
Providing low-cost remote Database Admin services]
Click here to join
Utah Oracle Users Group on Tek-Tips if you use
Oracle in
Utah USA.