Oracle 视图 V$DATAFILE_COPY 官方解释，作用，如何使用详细说明
本站中文解释
Oracle 视图 V$DATAFILE_COPY代表当前数据库中的备份数据文件的实例。相关的列有FILE#（文件ID），STATUS（状态），CHECKPOINT_CHANGE#（检查点变化#），CHECKPOINT_TIME（检查点时间），COPY_KEYWORDS（复制关键字）等。
使用它可以轻松跟踪数据文件的备份情况，例如检查哪些文件已成功备份、什么时候备份等。可以使用以下查询来获取备份数据文件的信息：
SELECT FILE#, STATUS, CHECKPOINT_CHANGE#, CHECKPOINT_TIME, COPY_KEYWORDS
FROM V$DATAFILE_COPY
ORDER BY FILE#;
官方英文解释
V$DATAFILE_COPY displays data file copy information from the control file.
| Column | Datatype | Description |
|---|---|---|
|
|
|
Data file copy record ID |
|
|
|
Data file copy record stamp |
|
|
|
File name of the data file copy. The maximum length of the name is operating system dependent. |
|
|
|
Data file copy tag |
|
|
|
Absolute data file number |
|
|
|
Tablespace relative data file number |
|
|
|
Data file creation change# |
|
|
|
Data file creation timestamp |
|
|
|
Resetlogs change number of the data file when the copy was made |
|
|
|
Resetlogs timestamp of the data file when the copy was made |
|
|
|
Normal full backups have a NULL value, level 0 incremental backups have a value of 0, and level 1 incremental backups have a value of 1 |
|
|
|
Checkpoint change number of the data file when the copy was made |
|
|
|
Checkpoint timestamp of the data file when the copy was made |
|
|
|
Highest change seen when the data file was copied |
|
|
|
Highest change written to the file by media recovery |
|
|
|
Timestamp of the highest change written to the file by media recovery |
|
|
|
( |
|
|
|
( |
|
|
|
Number of blocks marked corrupt by this copy operation. That is, blocks that were not marked corrupted in the source data file, but were detected and marked as corrupted during the copy operation. |
|
|
|
Total number of media corrupt blocks. For example, blocks with checksum errors are marked media corrupt. |
|
|
|
Total number of logically corrupt blocks. For example, applying redo for unrecoverable operations will mark affected blocks logically corrupt. |
|
|
|
Size of the data file copy in blocks (also the size of the data file when the copy was made) |
|
|
|
Block size of the data file |
|
|
|
RECID of the oldest offline range record in this control file copy; 0 for data file copies |
|
|
|
( |
|
|
|
Identifies the status of this data file copy. Possible values are:
|
|
|
|
Time when the copy was completed |
|
|
|
|
|
|
|
( |
|
|
|
If |
|
|
|
Lists additional retention options for this backup set. Possible values are:
|
|
|
|
Indicates whether RMAN scanned the file ( |
|
|
|
Indicates whether the file was created in the fast recovery area ( |
|
|
|
Owning |
|
|
|
Owning |
|
|
|
( |
|
|
|
If the value of the |
|
|
|
Foreign DBID from which this data file came from. The value is 0 if this file is not a foreign database file. |
|
|
|
|
|
|
|
SCN at which the foreign data file was transported into the database. The value is 0 if this file is not a foreign database file. |
|
|
|
The SCN of the |
|
|
|
The time of the |
|
|
|
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:
|
|
|
|
Recovery Manager (RMAN) allows a PDB to be backed up in two ways. The value in this column indicates how the PDB backup was taken:
|
|
|
|
Indicates whether the file is sparse ( |
|
|
|
The GUID of the PDB to which the backup belongs. This is useful after the PDB is dropped to identify which PDB the backup belongs to. |
