1Z0-043 · Question #177
Your database operates in ARCHIVELOG mode and all the tablespaces are online. Due to a user error, you decided to perform an incomplete recovery. Which two tasks would you be required to perform in…
The correct answer is B. open the database with the RESETLOGS option D. recover all the data files to the same system change number (SCN). See the full explanation below for the reasoning.
Question
Your database operates in ARCHIVELOG mode and all the tablespaces are online. Due to a user error, you decided to perform an incomplete recovery. Which two tasks would you be required to perform in the recovery process? (Choose two.)
Options
- Aopen the database with the RESTRICTED option
- Bopen the database with the RESETLOGS option
- Crecover to the required SCN only that data file in which the error occurred
- Drecover all the data files to the same system change number (SCN)
How the community answered
(23 responses)- A17% (4)
- B78% (18)
- C4% (1)
Community Discussion
10
Lena V.Jun 27, 2026B and D are your answers. Incomplete recovery means you are not applying all available redo, so Oracle has no way to guarantee consistency unless every single data file is rolled forward to the exact same SCN, which is why D is required and C will get you nowhere on the exam. Once you finish that recovery, Oracle will not let you open the database normally because the redo stream has been interrupted, so you are forced to use RESETLOGS, which resets the log sequence and starts a new database incarnation. A is a trap because RESTRICTED is used for limiting user access during certain admin tasks, not as part of the incomplete recovery process itself. Know this cold: incomplete recovery always ends with OPEN RESETLOGS, no exceptions.
Luis F.Jun 29, 2026Just to add one more thing Lena, if you are doing the recovery in RMAN you can also use the UNTIL SCN or UNTIL TIME or UNTIL SEQUENCE clauses to control exactly where the incomplete recovery stops, which the exam might test as a separate question from the RESETLOGS concept itself.
Orla P.Jun 27, 2026Saw this exact setup my first Oracle attempt, panicked on C, passed when I remembered all files need the same SCN before RESETLOGS.
Dragan P.Jun 28, 2026Close enough to pass the exam, but the pedantic truth is the control file checkpoint SCN is the arbiter here, not the datafile headers agreeing with each other, which is why a corrupted control file recreated with NORESETLOGS can still fool you into thinking you are consistent when you are not.
Luis F.Jun 27, 2026I totally picked A and C at first because I figured you would just restore the one messed-up data file and open in restricted mode for safety, but then I remembered that incomplete recovery means you are rolling back to a point in time, so every single data file has to land on the exact same SCN or your database is inconsistent, and after that kind of recovery Oracle forces you to open with RESETLOGS to wipe the old log sequence and start fresh, which is why the answers are B and D.
Orla P.Jun 29, 2026Luis, that is exactly right on the SCN consistency piece, and the one thing worth adding is that RESETLOGS is not just a safety measure Oracle forces on you, it is what establishes the new incarnation of the database so any archived logs from before that point are no longer valid for recovery.
Viktor S.Jun 22, 2026Why would recovering just one data file cause problems with SCN consistency across the whole database?
Luis F.Jun 25, 2026Yeah because that one file comes back at an older SCN than every other datafile, and Oracle expects all of them to match the same checkpoint SCN, so until you apply redo to roll that file forward to the current SCN the database sees the whole thing as inconsistent and refuses to open.
Dragan P.Jun 27, 2026Been doing RMAN recoveries since before half you folks knew what a control file was, and I am picking A and D here without blinking. When you drop the database into incomplete recovery you are restoring to a point in time before the current online redo logs are usable, which means Oracle has no business letting normal users connect until a DBA signs off on the state of that instance. RESTRICTED mode is your gate, it keeps connections limited to RESTRICTED SESSION privilege holders while you verify the recovery went where you wanted it to go before you expose it to the application tier. People keep skipping A because they confuse the open step with the RESETLOGS step and think those two are the same conversation, but restricted open and RESETLOGS open are separate decisions with separate purposes. D is mandatory because incomplete recovery is all-or-nothing across the database, every data file has to land on the same target SCN or you have a logically inconsistent database and Oracle will refuse to open it anyway, there is no such thing as recovering only the one file that got hit by the user error like option C is trying to sell you.
Lena V.Jun 28, 2026Dragan, your logic on D is solid, but the required open step after incomplete recovery is RESETLOGS, which is B, not RESTRICTED mode, because Oracle mandates ALTER DATABASE OPEN RESETLOGS to reset the log sequence and invalidate the old redo stream, and while opening in restricted mode is a sensible precaution it is not what the exam tests as a mandatory requirement here. RESTRICTED session is a procedural choice you can layer on top, but RESETLOGS is the non-negotiable gate Oracle enforces after any incomplete recovery.