| DEST_ID | NUMBER | Log archive destination parameter identifier ( 1to31) | 
| DEST_NAME | VARCHAR2(256) | Log archive destination parameter name | 
| STATUS | VARCHAR2(9) | Identifies the current status of the destination: 
VALID- Initialized and available
INACTIVE- No destination information
DEFERRED- Manually disabled by the user
ERROR- Error during open or copy
DISABLED- Disabled after error
BAD PARAM- Parameter has errors
ALTERNATE- Destination is in an alternate state
FULL- Exceeded quota size for the destination
 | 
| BINDING | VARCHAR2(9) | Specifies how failure will affect the archival operation: | 
| NAME_SPACE | VARCHAR2(7) | Identifies the scope of parameter setting: | 
| TARGET | VARCHAR2(7) | Specifies whether the archive destination is local or remote to the primary database: 
PRIMARY- local
STANDBY- remote
 | 
| ARCHIVER | VARCHAR2(10) | Identifies the archiver process relative to the database where the query is issued: | 
| SCHEDULE | VARCHAR2(8) | Indicates whether the archival of this destination is INACTIVE,PENDING,ACTIVE, orLATENT | 
| DESTINATION | VARCHAR2(256) | Specifies the location where the archived redo logs are to be archived | 
| LOG_SEQUENCE | NUMBER | Identifies the sequence number of the last archived redo log to be archived | 
| REOPEN_SECS | NUMBER | Identifies the retry time (in seconds) after error | 
| DELAY_MINS | NUMBER | Identifies the delay interval (in minutes) before the archived redo log is automatically applied to a standby database | 
| MAX_CONNECTIONS | NUMBER | Maximum number of connections | 
| NET_TIMEOUT | NUMBER | Number of seconds the log writer process will wait for status from the network server of a network operation issued by the log writer process | 
| PROCESS | VARCHAR2(10) | Identifies the archiver process relative to the primary database, even if the query is issued on the standby database: | 
| REGISTER | VARCHAR2(3) | Indicates whether the archived redo log is registered in the remote destination control file ( YES) or not (NO). If the archived redo log is registered, it is available to log apply services. | 
| FAIL_DATE | DATE | Date and time of last error | 
| FAIL_SEQUENCE | NUMBER | Sequence number of the archived redo log being archived when the last error occurred | 
| FAIL_BLOCK | NUMBER | Block number of the archived redo log being archived when the last error occurred | 
| FAILURE_COUNT | NUMBER | Current number of contiguous archival operation failures that have occurred for the destination | 
| MAX_FAILURE | NUMBER | Allows you to control the number of times log transport services will attempt to reestablish communication and resume archival operations with a failed destination | 
| ERROR | VARCHAR2(256) | Displays the error text | 
| ALTERNATE | VARCHAR2(256) | Alternate destination, if any | 
| DEPENDENCY | VARCHAR2(256) | Reserved for future use | 
| REMOTE_TEMPLATE | VARCHAR2(256) | Specifies the template to be used to derive the location to be recorded | 
| QUOTA_SIZE | NUMBER | Destination quotas, expressed in bytes | 
| QUOTA_USED | NUMBER | Size of all the archived redo logs currently residing on the specified destination | 
| MOUNTID | NUMBER | Instance mount identifier | 
| TRANSMIT_MODE | VARCHAR2(12) | Specifies network transmission mode: 
SYNCHRONOUS
PARALLELSYNC
ASYNCHRONOUS
 | 
| ASYNC_BLOCKS | NUMBER | Number of blocks specified for the ASYNCattribute | 
| AFFIRM | VARCHAR2(3) | Specifies disk I/O mode | 
| TYPE | VARCHAR2(7) | Indicates whether the archived log destination definition is PUBLICorPRIVATE. OnlyPUBLICdestinations can be modified at runtime using theALTER SYSTEM SETorALTER SESSION SETstatements. By default, all archived log destinations arePUBLIC. | 
| VALID_NOW | VARCHAR2(16) | Indicates whether the destination is valid right now for archival operations: 
YES- Redo log type and database role for this destination are valid for the current database
WRONG VALID_TYPE- Redo log type specified for this destination is not valid for the current database role. For example,WRONG VALID_TYPEwould be returned if a destination specified with theVALID_FOR=(STANDBY_LOGFILE,STANDBY_ROLE)attribute is running in the standby database role but does not have standby redo logs implemented.
WRONG VALID_ROLE- Database role specified for this destination is not the role in which the database is currently running. For example, the WRONGVALID_ROLEwould be returned when a destination defined with theVALID_FOR=(ONLINE_LOGFILE,STANDBY_ROLE)attribute is running in the primary database role.
INACTIVE- Destination is inactive, probably due to an error
 | 
| VALID_TYPE | VARCHAR2(15) | Redo log type or types that are valid for the destination: 
ONLINE_LOGFILE
STANDBY_LOGFILE
ALL_LOGFILES
 | 
| VALID_ROLE | VARCHAR2(12) | Database role or roles that are valid for the destination: 
PRIMARY_ROLE
STANDBY_ROLE
ALL_ROLES
 | 
| DB_UNIQUE_NAME | VARCHAR2(30) | Unique database name | 
| VERIFY | VARCHAR2(3) | Indicates whether the value of the VERIFYattribute on theLOG_ARCHIVE_DEST_nparameter is verified (YES) or not verified (NO) | 
| COMPRESSION | VARCHAR2(7) | Indicates whether network compression is ENABLEDorDISABLED. | 
| APPLIED_SCN | NUMBER | For a destination that corresponds to a physical or logical standby database, the SCN of the last applied redo. For a destination that corresponds to a snapshot standby database, the SCN of the last redo applied before conversion to a snapshot standby database. This column is only valid for enabled and active standby database destinations on a primary or cascading standby database. |