A database is running In ARCHIVELOG mode. It has two online redo log groups and each
group has one member.
A LGWR Input/output (I/O) fells due to permanent media failure that has resulted In the loss
of redo log file and the LWGR terminates causing the instance to crash. The steps to recover
from the loss of a current redo log group member in the random order are as follow.
1) Restore the corrupted redo log group.
2) Restore from a whole database backup.
3) Perform incomplete recovery.
4) Relocate by renaming the member of the damaged online redo log group to a new
location.
5) Open the database with the RESETLOGS option.
6) Restart the database instance.
7) Issue a checkpoint and clear the log.
Identify the option with the correct sequential steps to accomplish the task efficiently.
A.
1, 3, 4, and 5
B.
7, 3, 4. and 5
C.
2, 3, 4, and 5
D.
7, 4, 3. and 5
E.
Only 6 is required
Explanation:
Recovering After Losing All Members of an Online Redo Log Group
If a media failure damages all members of an online redo log group, then different scenarios
can occur depending on the type of online redo log group affected by the failure and the
archiving mode of the database.
If the damaged online redo log group is current and active, then it is needed for crash
recovery; otherwise, it is not. Table 30-4 outlines the various recovery scenarios.
