V$ARCHIVED_LOG: Archived Log Information from Control File

Share this article :

V$ARCHIVED_LOG displays archived log information from the control file, including archive log names. An archive log record is inserted after the online redo log is successfully archived or cleared (name column is NULL if the log was cleared). If the log is archived twice, there will be two archived log records with the same THREAD#, SEQUENCE#, and FIRST_CHANGE#, but with a different name. An archive log record is also inserted when an archive log is restored from a backup set or a copy and whenever a copy of a log is made with the RMAN COPY command.


Archived log record ID


Archived log record stamp


Archived log file name. If set to NULL, the log file was cleared before it was archived.


Original destination from which the archivelog was generated. The value is 0 if the destination identifier is not available.


Redo thread number


Redo log sequence number


Resetlogs change# of the database when the log was written


Resetlogs time of the database when the log was written


Resetlogs identifier associated with the archived redo log


First change# in the archived log


Timestamp of the first change


First change in the next log


Timestamp of the next change


Size of the archived log (in blocks)


Redo log block size. This is the logical block size of the archived log, which is the same as the logical block size of the online log from which the archived log was copied. The online log logical block size is a platform-specific value that is not adjustable by the user.


Creator of the archivelog:
• ARCH – ARCH process

• FGRD – Foreground process


• SRMN – RMAN at standby

• LGWR – LGWR process


Registrar of the entry:

• ARCH – ARCH process

• FGRD – Foreground process


• SRMN – RMAN at standby

• LGWR – LGWR process


Indicates whether the entry is an archivelog destination (YES) or not (NO)


Indicates whether the online redo log was archived (YES) or whether RMAN only inspected the log and created a record for future application of redo logs during recovery (NO).


Indicates whether the archivelog has been applied to its corresponding standby database (YES) or not (NO). The value is always NO for local destinations. This column is meaningful at the physical standby site for the ARCHIVED_LOG entries with REGISTRAR=’RFS’ (which means this log is shipped from the primary to the standby database). If REGISTRAR=’RFS’ and APPLIED is NO, then the log has arrived at the standby but has not yet been applied. If REGISTRAR=’RFS’ and APPLIED is YES, the log has arrived and been applied at the standby database. You can use this field to identify archivelogs that can be backed up and removed from disk.


Indicates whether an RMAN DELETE command has physically deleted the archived log file from disk, as well as logically removing it from the control file of the target database and from the recovery catalog (YES) or not (NO)


Status of the archived log:
• A – Available

• D – Deleted

• U – Unavailable

• X – Expired


Time when the archiving completed


Indicates whether the log contains the start of a LogMiner dictionary (YES) or not (NO)


Indicates whether the log contains the end of a LogMiner dictionary (YES) or not (NO)


Indicates whether the archived redo log contains the end of all redo information from the primary database (YES) or not (NO)


Indicates the number of times this file has been backed up. Values range from 0-15. If the file has been backed up more than 15 times, the value remains 15.


Redo thread number of the instance that performed the archival operation. This column differs from the THREAD# column only when a closed thread is archived by another instance.


Number assigned to the database instantiation


Indicates whether the file was created in the flash recovery area (YES) or not (NO)


Indicates whether the archive log was generated as the result of a FAL request (YES) or not (NO)

Related posts

Oracle SGA Memory Data Structure
ORA-28001: the password has expired
Get the Oracle Hostname & IP Address
SP2-0750: You may need to set ORACLE_HOME to your Oracle
© 2018 ITsiti. All Rights Reserved
Powered by KEEM