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” is correct.
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.
https://docs.oracle.com/cd/B28359_01/server.111/b28310/archredo006.htm#ADMIN11346
“D” is correct.
http://docs.oracle.com/cd/B28359_01/server.111/b28310/archredo006.htm#ADMIN11346
>>If any MANDATORY destination fails, including a MANDATORY standby destination,
>>Oracle Database ignores the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter.
Because “LOG_ARCHIVE_DEST_I parameter Is not available”, so “The destination set by the LOG_ARCHIVE_DEST_1 parameter is ignored “
You’re wrong:
MANDATORY
Specifies that filled online log files must be successfully archived to the destination before they can be reused. (https://docs.oracle.com/cd/B28359_01/server.111/b28294/log_arch_dest_param.htm#i77784)
A is the most appropriate answer.