Examine this configuration: 1. CDB1 is a container database running in ARCHIVELOG mode. 2. Multiple uncommitted transactions are running in CDB1. 3. Redo log groups 1 and 2 are INACTIVE. 4. Redo log…

Question

Options

• A1, 3, 5, 8, 6, 10
• B1, 3, 5, 6, 10
• C1, 3, 5, 7, 10
• D1, 2, 5, 7, 4, 10
• E1, 3, 5, 6, 9

• A
  16% (9)
• B
  67% (37)
• C
  2% (1)
• D
  5% (3)
• E
  9% (5)

Explanation

Option B is correct because losing the current, unarchived redo log group forces incomplete recovery - you mount the database, restore from backup, use RECOVER DATABASE NOREDO to apply only archived logs (explicitly skipping the missing online redo), then open with RESETLOGS to reset the log sequence after incomplete recovery.

Why the distractors fail:

• A adds RESTORE ARCHIVELOG ALL (step 8), which is redundant - RMAN's RECOVER DATABASE automatically restores needed archive logs internally, making step 8 an unnecessary extra step.
• C uses RECOVER DATABASE UNTIL AVAILABLE (step 7) instead of NOREDO - this form does not explicitly suppress access to online redo logs, which would cause an error since group 3 is physically missing.
• D uses STARTUP NOMOUNT (step 2) instead of STARTUP MOUNT - RESTORE DATABASE requires the database to be in MOUNT state, not NOMOUNT; additionally, the steps are ordered illogically.
• E uses ALTER DATABASE OPEN (step 9) without RESETLOGS - after any incomplete recovery, Oracle requires RESETLOGS to reset the redo log sequence; a plain open will fail.

Memory tip: When the current redo log is lost before archiving, remember the acronym "SMRR" - Shutdown abort → Mount → Restore → Recover NOREDO → RESETLOGS. The two R's at the end remind you: no Redo, Reset Logs.

No community discussion yet for this question.