Recovery Catalog Views, 2 of 28

RC_ARCHIVED_LOG

This view contains historical information about archived and unarchived redo logs. It corresponds to the V$ARCHIVED_LOG view in the target database control file.

Oracle inserts an archived redo log record after the online redo log is successfully archived or cleared (NAME column is NULL if the log was cleared). If the log is archived multiple times, then the view will contain multiple archived log records with the same THREAD#, SEQUENCE#, and RESETLOGS_CHANGE#, but with a different name. An archived log record is also inserted when an archived log is restored from a backup set or a copy. Note that an archived log can have no record if the record ages out of the control file.

Column	Datatype	Description
`DB_KEY`	`NUMBER`	The primary key for the target database. Use this column to form a join with almost any other catalog view.
`DBINC_KEY`	`NUMBER`	The primary key for the incarnation of the target database to which this record belongs. Use this column to form a join with `RC_DATABASE_INCARNATION`.
`DB_NAME`	`VARCHAR2(8)`	The `DB_NAME` of the database incarnation to which this record belongs.
`AL_KEY`	`NUMBER`	The primary key of the archived redo log in the recovery catalog. If you issue the `LIST` command while connected to the recovery catalog, this value appears in the `KEY` column of the output.
`RECID`	`NUMBER`	The archived redo log `RECID` from `V$ARCHIVED_LOG`. `RECID` and `STAMP` form a concatenated primary key that uniquely identifies this record in the target database control file.
`STAMP`	`NUMBER`	The archived redo log stamp from `V$ARCHIVED_LOG`. `RECID` and `STAMP` form a concatenated primary key that uniquely identifies this record in the target database control file.
`NAME`	`VARCHAR2(1024)`	The filename of the archived redo log.
`THREAD#`	`NUMBER`	The number of the redo thread.
`SEQUENCE#`	`NUMBER`	The log sequence number.
`RESETLOGS_CHANGE#`	`NUMBER`	The SCN of the most recent `RESETLOGS` when the record was created.
`RESETLOGS_TIME`	`DATE`	The time stamp of the most recent `RESETLOGS` when the record was created.
`FIRST_CHANGE#`	`NUMBER`	The first SCN of this redo log.
`FIRST_TIME`	`DATE`	The time when Oracle switched into the redo log.
`NEXT_CHANGE#`	`NUMBER`	The first SCN of the next redo log in the thread.
`NEXT_TIME`	`DATE`	The first time stamp of the next redo log in the thread.
`BLOCKS`	`NUMBER`	The size of this archived log in operating system blocks.
`BLOCK_SIZE`	`NUMBER`	The size of the block in bytes.
`COMPLETION_TIME`	`DATE`	The time when the redo log was archived or copied.
`ARCHIVED`	`VARCHAR2(3)`	Indicates whether the log was archived: `YES` (archived redo log) or `NO` (inspected file header of online redo log and added record to `V$ARCHIVED_LOG`). Inspecting the online logs creates archived log records for them, which allows them to be applied during RMAN recovery. Oracle sets `ARCHIVED` to `NO` to prevent online logs from being backed up.
`STATUS`	`VARCHAR2(1)`	The status of the archived redo log: `A` (available), `U` (unavailable), `D` (deleted), or X (expired).
`IS_STANDBY`	`VARCHAR2(3)`	The database that archived this log: `Y` (belongs to a standby database) or `N` (belongs to the primary database).
`DICTIONARY_BEGIN`	`VARCHAR2(3)`	Indicates whether this archived log contains the start of a LogMiner dictionary: `YES` or `NO`. If both `DICTIONARY_BEGIN` and `DICTIONARY_END` are `YES`, this log contains a complete LogMiner dictionary. If `DICTIONARY_BEGIN` is `YES` but `DICTIONARY_END` is `NO`, this log contains the start of the dictionary, and it continues through each subsequent log of this thread and ends in the log where `DICTIONARY_END` is `YES`.
`DICTIONARY_END`	`VARCHAR2(3)`	Indicates whether this archived log contains the end of a LogMiner dictionary: `YES` or `NO`. See the description of `DICTIONARY_BEGIN` for an explanation of how to interpret this value.