Your database is running in archivelog mode. Examine the parameters for your database instance:
LOG_ARCHIVE_DEST_l =’LOCATION=/disk1/arch MANDATORY’
LOG_ARCHIVE_DEST_2 =’LOCATION=/disk2/arch’
LOG_ARCHIVE_DEST_3 =’LOCATIO=/disk3/arch’LOG_ARCHIVE_DEST _4 =’LOCATIONs/disk4/arch’
LOG_ARCHIVE _MIN_SUCCEED_DEST = 2
While the database is open, you notice that the destination set by the log_archive_dest_1 parameter is not available. All redo log groups have been used.
What happens at the next log switch? smaller number of destinations
A.
The database instance hangs and the redo log files are not overwritten.
B.
The archived redo log files are written to the fast recovery area until the mandatory destination is made available.
C.
The database instance is shutdown immediately.
D.
The destination set by the log_archive_dest parameter is ignored and the archived redo log files are created in the next two available locations to
guarantee archive log success.
Explanation:
The database must archive to the destinations you specify as MANDATORY, regardless of whether you set LOG_ARCHIVE_MIN_SUCCEED_DEST to archive to a