You configured the Flash Recovery Area for your database. The database instance has been
started in ARCHIVELOG mode and the LOG_ARCHIVE_DEST_1 parameter is not set.
What will be the implications on the archiving and the location of archive redo log files?
A.
Archiving will be disabled because the destination for the redo log files is missing
B.
The database instance will shut down and the error details will be logged in the alert log file
C.
Archiving will be enabled and the destination for the archived redo log file will be set to the
Flash Recovery Area implicitly
D.
Archiving will be enabled and the location for the archive redo log file will be created in the
default location $ORACLE_HOME/log
Explanation:
LOG_ARCHIVE_DEST_n
The LOG_ARCHIVE_DEST_n parameters (where n = 1, 2, 3, … 10) define up to ten archive log
destinations.
The parameter integer suffix is defined as the handle displayed by the V$ARCHIVE_DEST
dynamic performance view.
Values:
SERVICE
Specifies a standby destination. Oracle Net (IPC or TCP) transmits the archivelog. A standby
instance must be associated with the destination. The value represented by tnsnames_service
corresponds to an appropriate service name in tnsnames.ora.
LOCATION
Specifies a local file system destination. You must specify this parameter for at least one
destination.
MANDATORY
Specifies that archiving to the destination must succeed before the redo log file can be made
available for reuse.
OPTIONAL
Specifies that successful archiving to the destination is not required before the redo log file can be
made available for reuse. If the “must succeed count,” set with
LOG_ARCHIVE_MIN_SUCCEED_DEST, is met, the redo logfile is marked for reuse. This is the
default.REOPEN
Specifies the minimum number of seconds before the archiver process (ARCn, foreground, or log
writer process) should try again to access a previously failed destination. Future attempts are
made when the next redo log file is archived. If a destination is MANDATORY, then Oracle
recommends that you specify a REOPEN time that reduces the possibility of primary database
shutdown due to lack of available online redo log files.
If you do not specify seconds, then the default value is 300