D. The distance (in bytes) between the checkpoint position in a redo log group and the end of the current redo log group can never be more than 90 percent of the size of the smallest redo log group

C. The failure of one statement is considered a statement failure, and one way to solve the problem is to enable resumable space allocation.

C. The parameter FAST_START_MTTR_TARGET specifies the desired time, in seconds, to recover a single instance from a crash or instance failure. The parameters LOG_CHECKPOINT_TIMEOUT and FAST_START_IO_TARGET can still be used in Oracle 10g but should only be used together in an advanced tuning scenario or for compatibility with older versions of Oracle. MTTR_ TARGET_ADVICE and FAST_START_TARGET_MTTR are not valid initialization parameters.

D. The PMON process periodically polls server processes to make sure that their sessions are still connected.

C. A DBA's disconnection of a session is an intentional process termination, not a failure. If a user's PC reboots, the user does not get a chance to log off, and the session is cleaned up by PMON; similarly, disconnecting from the application or SQL*Plus before logging out is considered a user process failure. A network problem can prematurely disconnect a user session, causing a user process failure. In all cases, PMON performs the session cleanup, whether the disconnection was intentional or not.

A, C. In addition to configuring a backup listener process and installing multiple network cards, you can also implement connect-time failover and a backup network connection to reduce the possibility of network failures.

B. The instance must be shut down, if it is not already down, to repair or replace the missing or damaged control file.

D. The distance between the checkpoint position in the redo log file and the end of the redo log group can never be more than 90 percent of the size of the smallest redo log group.

B, E. If a tablespace is taken offline because a datafile is missing, the instance can still be started as long as the missing datafile does not belong to the SYSTEM or UNDO tablespace.

A. If a network card fails, the failure type is network; the actual media containing the database files are not affected.

B, C. Only the SYSTEM and UNDO tablespaces require the instance to be shut down when their datafiles need recovery.

D. Unlike recovery of non–system-critical tablespaces other than SYSTEM or UNDO that can be recovered with the database in the OPEN state, the database must be in the MOUNT state to recover either the SYSTEM or UNDO tablespace.

A. If the redo log file group member has been lost due to a media failure or inadvertent deletion, the STATUS column is set to INVALID when an attempt is made to write redo information to that member.

B. Instance recovery, also known as crash recovery, occurs when the DBA attempts to open the database, but the files were not synchronized to the same SCN when the database was shut down. Once the DBA issues the STARTUP command, Oracle uses information in the redo log files to restore the datafiles (including the undo tablespace's datafiles) to the state before the instance failure. Oracle then uses undo data in the undo tablespace to roll back uncommitted transactions.

B. If the redo log file group member has never been used, either due to a new redo log file group or a repaired member, the value of STATUS is STALE until the log file member is used to record redo information.

C. In addition to reporting the first missing file to the administrator and listing all the missing files in the dynamic performance view V$RECOVER_FILE, the missing datafile(s) are noted in the DBWR background process trace files.

B. The loss of one or more of a tablespace's datafiles does not prevent other users from doing their work in other tablespaces. Recovering the affected datafiles can continue while the database is still online and available.

A. The dynamic performance view V$RECOVER_FILE contains a list of the datafiles that either need media recovery or are missing when the instance is started.

B. The primary failure in this scenario is instance. Subsequently, a network failure will occur when connections are attempted through the burned-out router. However, no connections are possible until the network card in the server is replaced; the instance cannot start because of a media failure on the disk containing the SYSTEM tablespace. It is assumed that the DBA has been configuring this database for fast recovery with both onsite and offsite backups to DVD and tape as well as sending the archived redo logs to a standby database.

D. All copies of the control files as defined in the SPFILE or the init.ora file must be identical and available. If one of the redo log file groups is missing a member, a warning is recorded in the alert log, but instance startup still proceeds. If the instance was previously shut down with SHUTDOWN ABORT, instance recovery automatically occurs during startup. Only an SPFILE or an init.ora file is needed to enter the NOMOUNT state, not both. If a tablespace is offline, the status of its datafiles is not checked until an attempt is made to bring it online; therefore, it will not prevent instance startup.