You have configured flash recovery area in your database and you set the following
Initialization parameters for your database instance:
LOG_ARCHIVE_DEST 1 = ‘LOCATION=/disk1/arch MANDATORY’
LOG _ARCHIEVE_DEST 2 = ‘LOCATION=/disk2/arch’
LOG_ARCHIVK_DEST_3 = ‘LOCATION=/diSk3/arch
LOG_ARCH1VK_DEST_4 = ‘LOCATION=/disk4/arch’
LOG_ARCHIVE_MIN-SUCCEED_DEST = 2
While the database instance is functional, you realized that the destination set by the
LOG_ARCHIVE_DEST_I parameter Is not available for the archived redo log file to be
created in. All redo log groups have been used.
What happens in an event of log switch?
A.
The online redo log file is not allowed to be overwritten.
B.
The archived redo log files are written to the flash recovery area until the MANDATORY
destination is made available.
C.
The database instance will crash because the archived redo log file cannot be created in
a destination set as MANDATORY.
D.
The destination set by the LOG_ARCHIVE_DEST_1 parameter is ignored and the
archived redo log files are created in the next two available locations to guarantee archive
log success.
A
if mandatory dest fails – online redo cannot be overwritten …
If the value of this parameter is less than the number of enabled, valid MANDATORY destinations, this parameter is ignored in favor of the MANDATORY destination count. If the value is more than the number of enabled, valid MANDATORY destinations, some of the enabled, valid OPTIONAL non-standby destinations are treated as MANDATORY.
You can switch dynamically from using the older parameters to the LOG_ARCHIVE_DEST_n parameter using ALTER SYSTEM, as follows:
1.Set LOG_ARCHIVE_MIN_SUCCEED_DEST to 1.
2.Set the value of LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST to the null string.
3.Set the desired number of destinations for the LOG_ARCHIVE_DEST_n parameters.
4.Reset LOG_ARCHIVE_MIN_SUCCEED_DEST to the desired value.
A
Database Administrator’s Guide: Managing Archive Destination Failure
The LOG_ARCHIVE_DEST_n parameter lets you specify whether a destination is OPTIONAL (the default) or MANDATORY. The LOG_ARCHIVE_MIN_SUCCEED_DEST=n parameter uses all MANDATORY destinations plus some number of non-standby OPTIONAL destinations to determine whether LGWR can overwrite the online log. The following rules apply:
Omitting the MANDATORY attribute for a destination is the same as specifying OPTIONAL.
You must have at least one local destination, which you can declare OPTIONAL or MANDATORY.
When you specify a value for LOG_ARCHIVE_MIN_SUCCEED_DEST=n, Oracle Database will treat at least one local destination as MANDATORY, because the minimum value for LOG_ARCHIVE_MIN_SUCCEED_DEST is 1.
If any MANDATORY destination fails, including a MANDATORY standby destination, Oracle Database ignores the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter.
The LOG_ARCHIVE_MIN_SUCCEED_DEST value cannot be greater than the number of destinations, nor can it be greater than the number of MANDATORY destinations plus the number of OPTIONAL local destinations.
If you DEFER a MANDATORY destination, and the database overwrites the online log without transferring the archived log to the standby site, then you must transfer the log to the standby manually.
the right answer is the A
The answer is A