This preview shows page 1. Sign up to view the full content.
Unformatted text preview: d data was written in order to supply the database
with all committed information to the time named, then the uncommitted transaction data
will be rolled back before the recovery ends. You might use time-based recovery to
resolve the following situations in your Oracle database: a user made unwanted data
changes or dropped a table, and you know approximately what time the mishap occurred;
a redo log that is not multiplexed is discovered to be corrupt, and you know what time the
redo log was archived.
A: If recovery is stopped by entering CANCEL at the recovery prompt, it's cancel-based
B: Recovery is stopped by pressing at <CTL-C> the recovery prompt is not time-based
recovery, but just user interrupted recovery of any type.
D: If recovery is stopped when the database has committed all changes up to the
specified system changes number (SCN), it is change-based incomplete recovery.
E: In the situation when recovery is stopped when the specified method of recovery
(CANCEL, TIME, or CHANGE), it is incomplete recovery, but not definitely time-based
recovery: it can be also cancel-based and change-based recovery.
View Full Document
This document was uploaded on 03/08/2014.
- Fall '09