RE: full recovery

AK,  

First, your normal backup should backup your database in the following order:  

Database, archivelogs and then control file. I actually do this in three separate Rman steps. This is so that the most recent control file is backups up after all of the data. This allows your to perform an incoimplete-recovery-restore to as late a time as possible. Also, consider adding a database trigger that, upon startup, perform an "alter database backup controlfile to trace;" Keep a copy of this trace file someplace safe as a sanity check. You could use it to recreate your controlfiles if all else fails.  

Your recovery steps are as follows:  

1. restore oracle software from tape.
2. restore config files ( init.ora , listener. ora ).
3. startup instance with nomount.
4. run Rman to restore the control file from tape.
5. Alter database mount
6. run Rman to restore database files
7. alter database open resetlogs.
8. perform a brand-new Rman backup (database, logs & controlfile)

turn the system back to the users (with many back-pats from management).  

You should be testing this on a regular basis.  

Good Luck!  

Tom Mercadante
Oracle Certified Professional

-----Original Message-----
Sent: Friday, October 24, 2003 2:15 PM
To: Multiple recipients of list ORACLE-L

Here is a scenerio :
I am taking full database backup everynight using rman to tape . which includes archive logs and control file. Not using catalog.Also have a backup of complete file system including oracle software and configuration files ( init.ora , listener.ora etc.. )
I lost the host on a particular day at 12 am afternoon. Now I want to restore this db to latest possible time to another host ( with same name ) Received on Fri Oct 24 2003 - 13:34:31 CDT