You database is running an ARCHIVELOG mode.
The following parameter are set in your database instance:
LOG_ARCHIVE_FORMAT = arch+%t_%r.arc
LOG_ARCHIVE_DEST_1 = ‘LOCATION = /disk1/archive’
DB_RECOVERY_FILE_DEST_SIZE = 50G
DB_RECOVERY_FILE = ‘/u01/oradata’
Which statement is true about the archived redo log files?
A.
They are created only in the location specified by the LOG_ARCHIVE_DEST_1 parameter.
B.
They are created only in the Fast Recovery Area.
C.
They are created in the location specified by the LOG_ARCHIVE_DEST_1 parameter and in
the default location $ORACLE_HOME/dbs/arch.
D.
They are created in the location specified by the LOG_ARCHIVE_DEST_1 parameter and the
location specified by the DB_RECOVERY_FILE_DEST parameter.
Explanation:
You can choose to archive redo logs to a single destination or to multiple
destinations.
Destinations can be local—within the local file system or an Oracle Automatic Storage
Management (Oracle ASM) disk group—or remote (on a standby database). When you
archive to multiple destinations, a copy of each filled redo log file is written to each
destination. These redundant copies help ensure that archived logs are always
available in the event of a failure at one of the destinations.
To archive to only a single destination, specify that destination using the LOG_ARCHIVE_DEST
and LOG_ARCHIVE_DUPLEX_DEST initialization parameters.
ARCHIVE_DEST initialization parameter. To archive to multiple destinations, you can
choose to archive to two or more locations using the LOG_ARCHIVE_DEST_n initialization
parameters, or to archive only to a primary and secondary destination using the LOG_
ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST initialization parameters.
[A] is correct.
A
If the parameter is DB_RECOVERY_FILE_DEST = ‘/u01/oradata’ the answer would be D.
If you specify both db_recovery_file_dest and log_archive_dest_n parameters without using the ‘location=use_db_recovery_file_dest’ trick, your archive logs will only go to the log_archive_dest_n location.
http://olearycomputers.com/ll/oracle/oracle_archivelog.html
But, the question says “DB_RECOVERY_FILE” i think that are one error here
A
A tested it. and s://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV89432
If you enable backup optimization, then RMAN does not back up a file to a device type if the identical file is already backed up on the device type.
Configuring Archived Redo Log Locations
Oracle recommends that you the use fast recovery area as an archiving location because the archived logs are automatically managed by the database. The generated file names for the archived logs in the fast recovery area are for Oracle Managed files and are not determined by the parameter LOG_ARCHIVE_FORMAT. Whatever archiving scheme you choose, it is always advisable to create multiple copies of archived redo logs.
You have the following basic options for archiving redo logs, listed from most to least recommended:
1.Enable archiving to the fast recovery area only and use disk mirroring to create the redundancy needed to protect the archived redo logs.
If DB_RECOVERY_FILE_DEST is specified and no LOG_ARCHIVE_DEST_n is specified, then LOG_ARCHIVE_DEST_10 is implicitly set to the recovery area. You can override this behavior by setting LOG_ARCHIVE_DEST_10 to an empty string.
2.Enable archiving to the fast recovery area and set other LOG_ARCHIVE_DEST_n initialization parameter to locations outside the fast recovery area.
If a fast recovery area is configured, then you can add the fast recovery area as an archiving destination by setting any LOG_ARCHIVE_DEST_n parameter to LOCATION=USE_DB_RECOVERY_FILE_DEST.
3.Set LOG_ARCHIVE_DEST_n initialization parameters to archive only to non-fast recovery area locations.
A
A