Lesson 7

In this module you learned about the concept of recovery and the required data structures to restore a NOARCHIVELOG database. The implications of recovery without archiving were explained as well as the steps to recover a database without archiving when a media failure occurs.
Having completed this module, you should be able to:
Identify data structures required for restore

1. Identify data structures required for recovery
2. Describe the implications of recovering a NOARCHIVELOG database
3. Recover a database in NOARCHIVELOG mode
4. Restore files to a different location if media failure occurs

This module introduced you to the following terms:

1. Restore: To restore means to bring back an original copy of a file from backup by issuing the operating system COPY command.
   Before recovery is performed, you need to restore the database.
2. Recover: To recover means to make all the restored files current to the same point in time.
3. Rolling forward: The process of recovering datafiles and control files by applying the redo logs is also known as rolling forward.
4. Log Writer (LGWR): Log Writer writes Redo Entries into the online redo logs. After a log fills, a log switch occurs. A minimum of two online redo logs is required by LGWR. Each log switch causes a new log sequence number to be used and assigned to the current log file.

In the next module, you will learn how to recover a database running in ARCHIVELOG mode. Before you go on to the next module, use the following Quiz and Exercise to check your understanding of the concepts presented in this module.

Click the Quiz link below to review your understanding of recovering a database without archiving.
Recovery Scenario - Quiz

Click the Exercise link below to practice the steps in recovering a NOARCHIVELOG database.
Conclusion - Exercise
For additional practice in recovering a NOARCHIVELOG database, try the
On Your Own exercise.