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
You place your database in ARCHIVELOG mode so that the redo logs are copied to a different location before being overwritten. So, you have to specify a location, where you want these redo logs to be archived. You may place them any where you like.
The Flash Recovery Area is merely a default location for version 10g archives.
“the LOG_ARCHIVE_DEST_1 parameter is not set” ==> so goes to the default
LOG_ARCHIVE_DEST is applicable only if you are running the database in ARCHIVELOG mode or are recovering a database from archived redo logs. LOG_ARCHIVE_DEST is incompatible with the LOG_ARCHIVE_DEST_n parameters, and must be defined as the null string (“”) or (‘ ‘) when any LOG_ARCHIVE_DEST_n parameter has a value other than a null string. Use a text string to specify the default location and root of the disk file or tape device when archiving redo log files. (Archiving to tape is not supported on all operating systems.) The value cannot be a raw partition.
If LOG_ARCHIVE_DEST is not explicitly defined and all the LOG_ARCHIVE_DEST_n parameters have null string values, LOG_ARCHIVE_DEST is set to an operating system-specific default value on instance startup.
By default, if the Flash recovery area is enabled, USE_DB_RECOVERY_FILE_DEST return Archive log file destination.