1Z0-032 · Question #104
When starting up the test database, you encounter the following error after mounting the database: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1…
The correct answer is D. Cancel-Based incomplete recovery. See the full explanation below for the reasoning.
Question
When starting up the test database, you encounter the following error after mounting the database:
ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/u01/oracle/app/oradata/log2.log' ORA-27037: unable to obtain file status While investigating the reason, you find that the status of the redo log group 2 is CURRENT. Which type of recovery would you perform to ensure that the database is functional?
Options
- AOpen Database recovery
- BTime-Based incomplete recovery
- Crecovery using the backup control file
- DCancel-Based incomplete recovery
- EChange-Based incomplete recovery
How the community answered
(48 responses)- A15% (7)
- B6% (3)
- C2% (1)
- D75% (36)
- E2% (1)
Community Discussion
2
Grace U.May 12, 2026The answer is D, Cancel-Based incomplete recovery, because the CURRENT redo log group is the one that was active when the instance went down and its file is now inaccessible, so you recover up to the last archived log and then issue CANCEL to stop before Oracle tries to apply the missing file, after which you open the database with RESETLOGS. Once you see CURRENT next to a lost log group, that tells you complete recovery is off the table and cancel-based is your clearest path forward.
Orla P.May 14, 2026Grace nailed the core logic, though worth noting that if you happened to have a multiplexed member of that CURRENT group on a separate disk that survived, complete recovery jumps back on the table before you reach for CANCEL.