DB_KEY

NUMBER

The primary key for the target database. Use this column to form a join with almost any other catalog view.

DBINC_KEY

NUMBER

The primary key for the incarnation of the target database. Use this column to form a join with RC_DATABASE_INCARNATION.

DB_NAME

VARCHAR2(8)

The DB_NAME of the database incarnation to which this record belongs.

CDF_KEY

NUMBER

The primary key of the datafile copy in the recovery catalog. If you issue the LIST command while connected to the recovery catalog, this value appears in the KEY column of the output.

RECID

NUMBER

The datafile copy record from V$DATAFILE_COPY. RECID and STAMP form a concatenated primary key that uniquely identifies this record in the target database control file.

STAMP

NUMBER

The datafile copy stamp from V$DATAFILE_COPY. RECID and STAMP form a concatenated primary key that uniquely identifies this record in the target database control file.

NAME

VARCHAR2(1024)

The filename of the datafile copy.

TAG

VARCHAR2(32)

The tag for the datafile copy.

FILE#

NUMBER

The absolute file number for the datafile.

CREATION_CHANGE#

NUMBER

The creation SCN of the datafile.

RESETLOGS_CHANGE#

NUMBER

The SCN of the most recent RESETLOGS when the datafile was created.

RESETLOGS_TIME

DATE

The time stamp of the most recent RESETLOGS in the datafile header.

INCREMENTAL_LEVEL

NUMBER

The incremental level of the copy: 0 or NULL.

CHECKPOINT_CHANGE#

NUMBER

The SCN of the most recent datafile checkpoint.

CHECKPOINT_TIME

DATE

The time of the most recent datafile checkpoint.

ABSOLUTE_FUZZY_CHANGE#

NUMBER

The highest SCN in any block of the file, if known. Recovery must proceed to at least this SCN for the file to become not fuzzy.

RECOVERY_FUZZY_CHANGE#

NUMBER

The SCN to which recovery must proceed for the file to become not fuzzy. If not NULL, this file must be recovered at least to the specified SCN before the database can be opened with this file.

RECOVERY_FUZZY_TIME

DATE

The time that is associated with the RECOVERY_FUZZY_CHANGE#.

ONLINE_FUZZY

VARCHAR2(3)

YES/NO. If set to YES, this copy was made after an instance failure or OFFLINE IMMEDATE (or is a copy that 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. To make this copy consistent, Recovery needs to apply all redo up to the marker that is placed in the redo stream when the ALTER TABLESPACE END BACKUP command is used.

BLOCKS

NUMBER

The number of blocks in the datafile copy (also the size of the datafile when the copy was made).

BLOCK_SIZE

NUMBER

The size of the blocks in bytes.

COMPLETION_TIME

DATE

The time when the copy completed.

STATUS

VARCHAR2(1)

The status of the copy: A (available), U (unavailable), X (expired), or D (deleted).

KEEP

VARCHAR2(3)

Indicates whether this copy has a retention policy different from the value for CONFIGURE RETENTION POLICY. Possible values are YES and NO.

KEEP_UNTIL

DATE

If the KEEP UNTIL TIME clause of the COPY command was specified, then this column shows the date after which this datafile copy becomes obsolete. If the column is NULL and KEEP OPTIONS is not NULL, the copy never becomes obsolete.

KEEP_OPTIONS

VARCHAR2(10)

The KEEP options specified for this datafile copy. Options can be LOGS (RMAN keeps the logs needed to recover this backup), NOLOGS (RMAN does not keep the logs needed to recover this backup), or NULL (the backup has no KEEP options and will be made obsolete based on the retention policy).

SCANNED

VARCHAR2(3)

Whether RMAN scanned the file (YES or NO). If YES, then this copy was created by a server process that examined every block in the file, for example, by the RMAN COPY or RESTORE command. If NO, then RMAN did not examine every block in the file, as when RMAN inspects a non-RMAN generated image copy or restores by proxy copy.

Whenever RMAN creates or restores a datafile copy, it adds rows to the V$DATABASE_BLOCK_CORRUPTION view and RC_DATABASE_BLOCK_CORRUPTION view if it discovers corrupt blocks in the file. If RMAN has scanned the entire file, then the absence of corruption records for this copy means that no corrupt blocks exist in the file. If RMAN did not scan the file, then the absence of corruption records means that corrupt blocks may or may not exist in the file.