Your database is in NOARCHIVELOG mode and a logswitch happens every 20 minutes. On Thursday
morning, media failure resulted in corruption of a data file belonging to the TOOLS tablespace.
Backups are taken on every Sunday. What would you do in this situation?
A.
recover using Oracle Flashback Database technology
B.
restore the data files from backup and perform a complete recovery
C.
restore only the corrupted data file and perform tablespace recovery
D.
restore the data files from backup and perform cancel-based recovery
E.
restore the entire database from the most recent backup and start the instance and open the
database
A log switch (switch, or change to another) occurs when LGWR stops writing to one redo log group and starts writing to another. By default, a log switch occurs automatically when the current redo log file group fills.
You can force a log switch to make the currently active group inactive and available for redo log maintenance operations. For example, you want to drop the currently active group, but are not able to do so until the group is inactive. You may also wish to force a log switch if the currently active group needs to be archived at a specific time before the members of the group are completely filled. This option is useful in configurations with large redo log files that take a long time to fill.
To force a log switch, you must have the ALTER SYSTEM privilege. Use the ALTER SYSTEM statement with the SWITCH LOGFILE clause.
MOST RECENT BACKUP
MOST RECENT BACKUP ON SUNDAY