Oracle 视图 V$PROXY_DATAFILE 官方解释,作用,如何使用详细说明
本站中文解释
Oracle V$PROXY_DATAFILE视图中的每一行记录均表示一个数据文件在proxy copy操作(数据库的文件拷贝操作)中的状态信息,此视图用于查询有关数据库文件在proxy copy操作中的状态信息。
使用方法:
1. 查看当前状态:
SELECT FILE_NAME, STATUS FROM V$PROXY_DATAFILE;
该查询语句会显示当前正在使用的数据文件以及每个文件的当前状态。
2. 查看历史状态:
SELECT FILE_NAME, PREVIOUS_STATUS, CURRENT_STATUS FROM V$PROXY_DATAFILE;
该查询语句会显示每个数据文件在proxy copy操作开始前ら处的状态,和在开始后的当前状态。
官方英文解释
V$PROXY_DATAFILE contains descriptions of datafile and control file backups that are taken with Proxy Copy. Each row represents a backup of one database file. | Column | Datatype | Description |
|---|---|---|
|
| Proxy copy record ID |
|
| Proxy copy record stamp |
|
| Type of the device on which the copy resides |
|
| Proxy copy handle identifies the copy for restore |
|
| Comment returned by the operating system or storage subsystem. This value is informational only. It is not needed for restore. |
|
| Name of the media on which the copy resides. This value is informational only. It is not needed for restore. |
|
| Media pool in which the copy resides. This is the same value that was entered in the |
|
| Proxy copy tag |
|
| Status of the backup set:
|
|
| Indicates whether this record has been deleted ( |
|
| Absolute datafile number, or 0 if this is a control file backup |
|
| Datafile creation change number |
|
| Datafile creation Timestamp |
|
| Resetlogs change number of the datafile when the copy was made |
|
| Resetlogs timestamp of the datafile when the copy was made |
|
| Checkpoint change number of the datafile when the copy was made |
|
| Checkpoint timestamp of the datafile when the copy was made |
|
| Highest change in any block of the file, if known |
|
| Highest change written to the file by media recovery |
|
| Timestamp of the highest change written to the file by media recovery |
|
| If this backup is part of an incremental backup strategy, then 0. Otherwise null. |
|
| Indicates whether this copy was made after a crash or offline immediate (or is a copy of a copy which was taken improperly while the database was open) ( |
|
| Indicates whether this is a copy taken using the |
|
| Size of the copy (in blocks). Also the size of the datafile when the copy was made. |
|
| Block size of the datafile |
|
| If the file number is |
|
| Starting time |
|
| Completion time |
|
| Number of elapsed seconds |
|
| Type of control file:
|
|
| Indicates whether this backup set has a retention policy that is different than the value for the configure retention policy ( |
|
| If specified, then this is the date after which the backup becomes obsolete. If this column is NULL, then the backup never expires. |
|
| Additional retention options for this backup set:
|
|
| Owning |
|
| Owning |
|
| Foreign DBID of the database from which this datafile was transported. The value is |
|
| Indicates whether this is a proxy copy of a transported read-only foreign file ( |
|
| SCN at which the foreign datafile was transported into the database. The value is |
|
| SCN of the |
|
| Time of the |
|
| 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:
|
|
| 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. |
扫码添加企业微信,预约演示。
