RC_BACKUP_COPY_DETAILS contains detailed information all AVAILABLE control file and data file copies. Columns SESSION_KEY, SESSION_RECID, SESSION_STAMP, and COPY_KEY uniquely identify an RMAN session and data file copy. Other columns for this view have the same semantics as in RC_DATAFILE_COPY.
This view is primarily intended to be used internally by Enterprise Manager.
| Column | Data Type | Description | 
|---|---|---|
| SESSION_KEY | NUMBER | Session identifier. Use in joins with RC_RMAN_OUTPUTandRC_RMAN_BACKUP_JOB_DETAILS. | 
| SESSION_RECID | NUMBER | Together with SESSION_STAMP, uniquely identifies output for this backup job fromRC_RMAN_OUTPUT. | 
| SESSION_STAMP | NUMBER | Together with SESSION_RECID, uniquely identifies output for this backup job fromRC_RMAN_OUTPUT. | 
| DB_KEY | NUMBER | The primary key for this database in the recovery catalog. Use this column to join with almost any other catalog view. | 
| DB_NAME | VARCHAR2(8) | The DB_NAMEof the database incarnation to which this record belongs. | 
| RSR_KEY | NUMBER | Unique key for the row in RC_RMAN_STATUScorresponding to the job that created this copy. | 
| COPY_KEY | NUMBER | Unique identifier for this data file or control file copy. | 
| FILE# | NUMBER | The absolute file number for the data file, for data file copies. | 
| NAME | VARCHAR2(1024) | The file name of the data file or control file copy. | 
| TAG | VARCHAR2(32) | The tag, if any, for this data file or control file copy. | 
| CREATION_CHANGE# | NUMBER | The creation SCN of the data file, for data files. | 
| CREATION_TIME | DATE | The creation time of the file. | 
| CHECKPOINT_CHANGE# | NUMBER | The SCN of the most recent data file checkpoint. | 
| CHECKPOINT_TIME | DATE | The time of the most recent data file checkpoint. | 
| MARKED_CORRUPT | NUMBER | Number of blocks in the data file that are marked corrupt, based on RC_DATABASE_BLOCK_CORRUPTIONview. | 
| OUTPUT_BYTES | NUMBER | Sum of sizes of all output pieces generated by this job. | 
| COMPLETION_TIME | DATE | The completion time for this file copy. | 
| CONTROLFILE_TYPE | VARCHAR2(1) | The type of control file backed up, for control file copies: B(normal copy) orS(standby copy). Otherwise,NULL. | 
| KEEP | VARCHAR2(3) | YES, if this copy has a retention policy different from the value forCONFIGURE RETENTION POLICY. Otherwise,NO. | 
| KEEP_UNTIL | DATE | If the KEEP UNTIL TIMEclause of theBACKUPcommand was specified, then this column shows the data after which this file copy becomes obsolete. If the column isNULLandKEEP_OPTIONSis not null, then this copy never becomes obsolete. | 
| KEEP_OPTIONS | VARCHAR2(11) | The KEEPoptions specified for this data file copy. Possible values areNOLOGS,BACKUP_LOGS,LOGS, andNULL.NOLOGSindicates a consistent backup made when the database was mounted.BACKUP_LOGSindicates that the backup while the database was open, so archived log backups must be applied to make it consistent.LOGSindicates a long-term backup made with theLOGSkeyword, which is now deprecated.NULLindicates that this backup has noKEEPoptions and becomes obsolete based on the backup retention policy. | 
| IS_RECOVERY_DEST_FILE | VARCHAR2(3) | YESif this copy is located in the fast recovery area. Otherwise,NO. | 
| OUTPUT_BYTES_DISPLAY | VARCHAR2(4000) | Same value as OUTPUT_BYTES, but converted to a user-displayable format, for example, 798.01M or 5.25G. |