标签：
本视图包含了归档重做日志文件的信息，如归档文件的名称、归档路径等。该视图中数据来自于控制文件，一般是当一个Online
Redologs完成归档后，就会在控制文件中插入一条记录，如果归档目录有多个的话，则同时插入对应数量的记录（当然路径肯定不同），另外当通过RMAN恢复归档文件或复制归档文件时，也会插入对应的记录。下面对一些经常使用的列进行说明。
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.
| Column | Datatype | Description |
|---|---|---|
RECID |
NUMBER |
Archived log record ID |
STAMP |
NUMBER |
Archived log record stamp |
NAME |
VARCHAR2(513) |
Archived log file name. If set to NULL, either the log file was cleared before it was archived or
an RMAN backup command with the "delete input" option was executed to back up archivelog all (RMAN> backup
archivelog all delete input;).记录归档文件路径和名称。 |
DEST_ID |
NUMBER |
Original destination from which the archive log was generated. The value is 0 if the destination identifier
is not available. |
THREAD# |
NUMBER |
Redo thread number 归档线程号，RAC环境下适用。 |
SEQUENCE# |
NUMBER |
Redo log sequence number 归档文件序号。 |
RESETLOGS_CHANGE# |
NUMBER |
Resetlogs change number of the database when the log was written |
RESETLOGS_TIME |
DATE |
Resetlogs time of the database when the log was written |
RESETLOGS_ID |
NUMBER |
Resetlogs identifier associated with the archived redo log |
FIRST_CHANGE# |
NUMBER |
First change number in the archived log |
FIRST_TIME |
DATE |
Timestamp of the first change 等同于创建时间。 |
NEXT_CHANGE# |
NUMBER |
First change in the next log |
NEXT_TIME |
DATE |
Timestamp of the next change |
BLOCKS |
NUMBER |
Size of the archived log (in blocks) |
BLOCK_SIZE |
NUMBER |
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 |
VARCHAR2(7) |
Creator of the archivelog:
ARCH：表示由归档进程创建。 FGRD：表示由前台进程创建。 RMAN：表示由RMAN创建。 SRMN：表示由Standby端的RMAN创建。 LGWR：表示由Logwriter进程创建。 |
REGISTRAR |
VARCHAR2(7) |
Registrar of the entry:
|
STANDBY_DEST |
VARCHAR2(3) |
Indicates whether the entry is an archivelog destination (YES) or not (NO) |
ARCHIVED |
VARCHAR2(3) |
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).
|
APPLIED |
VARCHAR2(9) |
Indicates whether an archived redo log file has been applied to the corresponding physical standby database. The value is always NO for
local destinations.
This column is meaningful on a physical standby database for rows where
This column can be used to identify log files that can be backed up and deleted. When used for this purpose, the value
是否被应用，Data Guard环境下适用。 |
DELETED |
VARCHAR2(3) |
Indicates whether an RMAN DELETEcommand 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 |
VARCHAR2(1) |
Status of the archived log:
A：指正常归档状态。 D：指该记录指向的归档文件已被删除。 U：指该记录指向的归档已不存用。 X：指该条记录失效，通常是当你在RMAN中执行了CROSSCHECK ARCHIVELOG后有可能出现。 |
COMPLETION_TIME |
DATE |
Time when the archiving completed |
DICTIONARY_BEGIN |
VARCHAR2(3) |
Indicates whether the log contains the start of a LogMiner dictionary (YES) or not (NO) |
DICTIONARY_END |
VARCHAR2(3) |
Indicates whether the log contains the end of a LogMiner dictionary (YES) or not (NO) |
END_OF_REDO |
VARCHAR2(3) |
Indicates whether the archived redo log contains the end of all redo information from the primary database (YES)
or not (NO) |
BACKUP_COUNT |
NUMBER |
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. |
ARCHIVAL_THREAD# |
NUMBER |
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. |
ACTIVATION# |
NUMBER |
Number assigned to the database instantiation |
IS_RECOVERY_DEST_FILE |
VARCHAR2(3) |
Indicates whether the file was created in the fast recovery area (YES) or not (NO) |
COMPRESSED |
VARCHAR2(3) |
Reserved for internal use |
FAL |
VARCHAR2(3) |
Indicates whether the archive log was generated as the result of a FAL request (YES) or not (NO) |
END_OF_REDO_TYPE |
VARCHAR2(10) |
Possible values are as follows:
|
BACKED_BY_VSS |
VARCHAR2(3) |
Whether or not the file has been backed up by Volume Shadow Copy Service (VSS). This column is reserved for internal use. |
标签：
原文地址：http://blog.csdn.net/jiaping0424/article/details/51339236
