Oracle 视图 V$ARCHIVED_LOG 官方解释，作用，如何使用详细说明
本站中文解释
V$ARCHIVED_LOG视图描述了系统中已经归档的日志文件的相关信息。归档日志是ARCHIVELOG模式的一种，用来记录DML以及DDL对数据库中对象所做的更改，保护数据库以及实施重做数据库恢复。
V$ARCHIVED_LOG视图获取归档日志中的：
– ARCHIVED和DELETED字段
– FLAGS, ARCHIVE_)SCN, ARCHIVE_DATE, REDO_THREAD, SEQUENCE#, and RESETLOGS_CHANGE#等字段
– SESSION_INFO字段
– 要归档的日志的状态信息
V$ARCHIVED_LOG视图的主要用途是查看已经归档的日志的信息，确定要恢复的日志。可以直接执行：
“`SQL
SELECT ARCHIVED, DELETED, SEQUENCE#, RESETLOGS_CHANGE#,
FLAGS, ARCHIVE_DATE, ARCHIVE_SCN, SESSION_INFO
FROM V$ARCHIVED_LOG;
“`
该语句可以查询当前被归档日志的相关信息。
官方英文解释
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 |
|---|---|---|
|
|
|
Archived log record ID |
|
|
|
Archived log record stamp |
|
|
|
Archived log file name. If set to |
|
|
|
Original destination from which the archive log was generated. The value is |
|
|
|
Redo thread number |
|
|
|
Redo log sequence number |
|
|
|
Resetlogs change number 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 number 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:
|
|
|
|
Registrar of the entry:
|
|
|
|
Indicates whether the entry is an archivelog destination ( |
|
|
|
Indicates whether the online redo log was archived ( |
|
|
|
Indicates whether an archived redo log file has been applied to the corresponding physical standby database. The value is always 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 |
|
|
|
Indicates whether an RMAN |
|
|
|
Status of the archived log:
|
|
|
|
Time when the archiving completed |
|
|
|
Indicates whether the log contains the start of a LogMiner dictionary ( |
|
|
|
Indicates whether the log contains the end of a LogMiner dictionary ( |
|
|
|
Indicates whether the archived redo log contains the end of all redo information from the primary database ( |
|
|
|
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 |
|
|
|
Number assigned to the database instantiation |
|
|
|
Indicates whether the file was created in the fast recovery area ( |
|
|
|
Reserved for internal use |
|
|
|
Indicates whether the archive log was generated as the result of a FAL request ( |
|
|
|
Possible values are as follows:
|
|
|
|
Whether or not the file has been backed up by Volume Shadow Copy Service (VSS). This column is reserved for internal use. |
|
|
|
The ID of the container to which the data pertains. Possible values include:
|
