RECID |
NUMBER |
Proxy copy record ID |
STAMP |
NUMBER |
Proxy copy record stamp |
DEVICE_TYPE |
VARCHAR2(17) |
Type of the device on which the copy resides |
HANDLE |
VARCHAR2(513) |
Proxy copy handle identifies the copy for restore |
COMMENTS |
VARCHAR2(81) |
Comment returned by the operating system or storage subsystem. This value is informational only; not needed for restore. |
MEDIA |
VARCHAR2(65) |
Name of the media on which the copy resides. This value is informational only; not needed for restore. |
MEDIA_POOL |
NUMBER |
The media pool in which the copy resides. This is the same value that was entered in the pool operand of the Recovery Manager backup command |
TAG |
VARCHAR2(32) |
Proxy copy tag |
STATUS |
VARCHAR2(1) |
Indicates the status of the copy:
A - The object is available
D - The object is deleted
X - The object has been "cross-checked" and found not to exist. A subsequent "delete expired" command will change the status to D . If, for some reason, the object really does still exist, then a subsequent "cross-check" command will change the status back to A .
|
FILE# |
NUMBER |
Absolute datafile number, or 0 if this is a control file backup |
CREATION_CHANGE# |
NUMBER |
Datafile creation change number |
CREATION_TIME |
DATE |
Datafile creation Timestamp |
RESETLOGS_CHANGE# |
NUMBER |
Resetlogs change number of the datafile when the copy was made |
RESETLOGS_TIME |
DATE |
Resetlogs timestamp of the datafile when the copy was made |
CHECKPOINT_CHANGE# |
NUMBER |
Checkpoint change number of the datafile when the copy was made |
CHECKPOINT_TIME |
DATE |
Checkpoint timestamp of the datafile when the copy was made |
ABSOLUTE_FUZZY_CHANGE# |
NUMBER |
The highest change in any block of the file, if known |
RECOVERY_FUZZY_CHANGE# |
NUMBER |
Highest change written to the file by media recovery |
RECOVERY_FUZZY_TIME |
DATE |
Timestamp of the highest change written to the file by media recovery |
INCREMENTAL_LEVEL |
NUMBER |
0 if this backup is part of an incremental backup strategy, otherwise NULL |
ONLINE_FUZZY |
VARCHAR2(3) |
(YES |NO ) If set to YES , 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). Recovery will need to apply all redo up to the next crash recovery marker to make the file consistent. |
BACKUP_FUZZY |
VARCHAR2(3) |
(YES |NO ) If set to YES , this is a copy taken using the BEGIN BACKUP|END BACKUP technique. Note that the BEGIN BACKUP|END BACKUP technique is used internally when proxy copies of open files are created. Recovery will need to apply all redo up to the end backup marker to make this copy consistent. |
BLOCKS |
NUMBER |
Size of the copy in blocks (also the size of the datafile when the copy was made) |
BLOCK_SIZE |
NUMBER |
Block size of the datafile |
OLDEST_OFFLINE_RANGE |
NUMBER |
If file# is 0 (ie, this is a control file backup), the RECID of the oldest offline range record in this control file copy. 0 for datafile copies. |
START_TIME |
DATE |
The starting time |
COMPLETION_TIME |
DATE |
The completion time |
ELAPSED_SECONDS |
NUMBER |
The number of elapsed seconds |
CONTROLFILE_TYPE |
VARCHAR2(1) |
B indicates normal copies
S indicates standby copies |
KEEP |
VARCHAR2(3) |
(YES |NO ) Indicates whether or not this backup set has a retention policy that is different than the value for the configure retention policy |
KEEP_UNTIL |
DATE |
If KEEP_UNTIL_TIME is specified, this is the date after which the backup becomes obsolete. If this column is null, then the backup never expires. |
KEEP_OPTIONS |
VARCHAR2(10) |
Lists additional retention options for this backup set. Possible values are:
LOGS - The logs need to recover this backup are kept
NOLOGS - The logs needed to recover this backup will not be kept |