Recovering a Database in NOARCHIVELOG Mode

In NOARCHIVELOG mode the recovery is very simple. All you have to do is to restore the database files from your backup to the original location  and start the database. If one of your data file got corrupted. The time try to start the Oracle Instance, it will give you an error. In this case shutdown the database. Restore all the data files, redo log files and control file back to their original location from your last whole/complete cold backup.Then start the Oracle database again and then connecting as SYSDBA.There are some steps as following:

1) If the database is open then shutdown the database
Shutdown immediate

2) If possible, correct the media problem so that the backup database files can be
restored to their original locations.
3) Restore the most recent whole database backup. Restore all of the
datafiles and control files of the whole database backup, not just the damaged
files. The following example restores a whole database backup:
% cp /opt/luck1/BACKUP/tbs* /opt/luck # restores datafiles
% cp /opt/luck1/BACKUP/cf.f /opt/luck # restores control file
4) Because online redo logs are not backed up, you cannot restore them with the
datafiles and control files. In order to allow Oracle to reset the online redo logs,
you must have to do incomplete recovery:
5) Open the database in RESETLOGS mode.

People who read this post also read :


Nice blog, and the information was very good.
Thanks for posting.

You can't recover a database in noarchivelog mode - you can only restore a database that is in noarchivelog mode - unless the database is recovering from a crash and it's using the redo logs to recover.

The title of your blog should be: How to Restore a Database in NOARCHIVELOG Mode.

Thanks for sharing for knowledge, yes you are saying right but in noarchivelog mode recovery is possible but only in that case in which log number is not switched

Post a Comment


Twitter Delicious Facebook Digg Stumbleupon Favorites More