1Z0-032 · Question #106
You observe that your senior database administrator is executing the following command, using Recovery Manager (RMAN), to perform an incomplete database recovery of the database at noon. on December…
The correct answer is D. to restore the database completely from the last available backup taken prior to the time specified in. See the full explanation below for the reasoning.
Question
You observe that your senior database administrator is executing the following command, using Recovery Manager (RMAN), to perform an incomplete database recovery of the database at noon. on December 9, 2012:
RMAN> RUN { ALLOCATE CHANNEL c1 TYPE DISK; SET UNTIL TIME = '2012-12-09:11:40:45'; RESTORE DATABASE; RECOVER DATABASE; } Your database is running in ARCHIVELOG mode. What could be the objective of specifying the SET UNTIL TIME option in the RUN block of RMAN?
Options
- Ato restore and recover the database from the time specified until the current operating system time
- Bto restore and recover the database between the time specified and the current operating system time
- Cto restore the database till the time specified and then start recovering the database until the current
- Dto restore the database completely from the last available backup taken prior to the time specified in
How the community answered
(50 responses)- A4% (2)
- B2% (1)
- C10% (5)
- D84% (42)
Community Discussion
6
Orla P.May 29, 2026D is the one to go with here. SET UNTIL TIME tells RMAN to use the last full backup taken before that timestamp as the restore point, so it pulls the datafiles from that prior backup and then rolls forward through archived logs only up to that moment, not beyond it, which is exactly what incomplete recovery means.
Prof. SaraMay 31, 2026SET UNTIL TIME does not select which backup to use, it sets the upper boundary for recovery, and RMAN's channel allocation picks the most recent backup that satisfies the until clause, so the roll-forward stops at that timestamp rather than the backup itself being "the restore point" in any formal sense.
Prof. SaraMay 23, 2026I almost circled A, but SET UNTIL TIME caps recovery at that SCN boundary, not the current time, so D wins.
Orla P.May 25, 2026Right, and the practical kicker is that if you omit the UNTIL TIME clause entirely you get full recovery to the last archived log, so specifying a time that predates your most recent archive is the only scenario where that SCN cap actually bites you.
Grace U.May 27, 2026The way I read it, SET UNTIL TIME anchors the starting point of the operation, so RMAN knows where to begin the restore and then carries the recovery forward from that timestamp all the way to the current OS time, which is exactly what option A describes. If the intent were just to cap the recovery at that moment rather than use it as a baseline, the command would not need both RESTORE and RECOVER in the same block.
Orla P.May 27, 2026Grace, SET UNTIL TIME actually sets a ceiling on the recovery, not a starting point, so RMAN stops applying redo logs at that timestamp rather than using it as a baseline. Option D is correct because the restore and recover both honor that upper boundary, leaving the database in an incomplete recovery state as of that moment in time.