1Z0-052 · Question #217
Your database is running in NOARCHIVELOG mode. You want to put the database in ARCHIVELOG mode. Which two statements regarding archive log destinations are true? (Choose two.)
The correct answer is C. A maximum of ten different destinations can be assigned. E. The destination may be local or remote for a Standby Database. Oracle supports up to ten archive log destinations configured via LOG_ARCHIVE_DEST_1 through LOG_ARCHIVE_DEST_10, and these destinations can be local disk paths or remote services including Standby Database targets.
Question
Your database is running in NOARCHIVELOG mode. You want to put the database in ARCHIVELOG mode. Which two statements regarding archive log destinations are true? (Choose two.)
Options
- AThe destination must be global only.
- BA maximum of five destinations can be assigned.
- CA maximum of ten different destinations can be assigned.
- DAll the destinations are determined by the server automatically.
- EThe destination may be local or remote for a Standby Database.
- FThe destination can be changed by setting the LOG_ARCHIVE_FORMAT initialization parameter.
How the community answered
(65 responses)- A2% (1)
- B12% (8)
- C77% (50)
- D3% (2)
- F6% (4)
Why each option
Oracle supports up to ten archive log destinations configured via LOG_ARCHIVE_DEST_1 through LOG_ARCHIVE_DEST_10, and these destinations can be local disk paths or remote services including Standby Database targets.
Archive log destinations are not restricted to a global scope - each LOG_ARCHIVE_DEST_n can independently specify a local path or a remote service, giving the DBA per-destination control.
The maximum number of configurable archive log destinations in Oracle (through 11g) is ten, not five - they are numbered LOG_ARCHIVE_DEST_1 through LOG_ARCHIVE_DEST_10.
Oracle provides exactly ten archive log destination parameters - LOG_ARCHIVE_DEST_1 through LOG_ARCHIVE_DEST_10 - allowing DBAs to send archived logs to multiple locations simultaneously. This ten-destination maximum is a defined limit of Oracle's archiving architecture through Oracle 11g.
Archive log destinations are not automatically determined by the server - the DBA must explicitly set each LOG_ARCHIVE_DEST_n parameter and its associated attributes.
LOG_ARCHIVE_DEST_n parameters accept both local directory paths and remote network service names specified via the SERVICE attribute, which is the mechanism used to ship redo logs to a Data Guard Standby Database over the network.
LOG_ARCHIVE_FORMAT defines the filename pattern template for archived redo log files (incorporating tokens like %t, %s, %r), not the directory or service destination where the files are written.
Concept tested: Oracle ARCHIVELOG mode archive log destinations configuration
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/LOG_ARCHIVE_DEST_n.html
Topics
Community Discussion
No community discussion yet for this question.