| DB_KEY | NUMBER | The primary key for the target database. Use this column to form a join with almost any other catalog view. | 
| DB_ID | NUMBER | The unique database identifier. | 
| BS_KEY | NUMBER | The primary key of the backup set in the recovery catalog. If you issue the LISTcommand while connected to the recovery catalog, this value appears in theKEYcolumn of the output. | 
| RECID | NUMBER | The backup set RECIDfromV$BACKUP_SET.RECIDandSTAMPform a concatenated primary key that uniquely identifies this record in the target database control file. Use eitherRECIDandSTAMPorSET_STAMPandSET_COUNTto accessV$BACKUP_SET. | 
| STAMP | NUMBER | The backup set STAMPfromV$BACKUP_SET.RECIDandSTAMPform a concatenated primary key that uniquely identifies this record in the target database control file. Use eitherRECIDandSTAMPorSET_STAMPandSET_COUNTto accessV$BACKUP_SET. | 
| SET_STAMP | NUMBER | The SET_STAMPvalue fromV$BACKUP_SET.SET_STAMPandSET_COUNTform a concatenated key that uniquely identifies this record in the target database control file. Use eitherRECIDandSTAMPorSET_STAMPandSET_COUNTto accessV$BACKUP_SET. | 
| SET_COUNT | NUMBER | The SET_COUNTvalue fromV$BACKUP_SET.SET_STAMPandSET_COUNTform a concatenated key that uniquely identifies this record in the target database control file. Use eitherRECIDandSTAMPorSET_STAMPandSET_COUNTto accessV$BACKUP_SET. | 
| BACKUP_TYPE | VARCHAR2(1) | The type of the backup: D(full backup or level 0 incremental),I(incremental level 1),L(archived redo log). | 
| INCREMENTAL_LEVEL | NUMBER | The level of the incremental backup: NULL,0, or 1. | 
| PIECES | NUMBER | The number of backup pieces in the backup set. | 
| START_TIME | DATE | The time when the backup began. | 
| COMPLETION_TIME | DATE | The time when the backup completed. | 
| ELAPSED_SECONDS | NUMBER | The duration of the backup in seconds. | 
| STATUS | VARCHAR2(1) | The status of the backup set: A(all backup pieces available),D(all backup pieces deleted),O(some backup pieces are available but others are not, so the backup set is unusable). | 
| CONTROLFILE_INCLUDED | VARCHAR2(7) | Possible values are NONE(backup set does not include a backup control file),BACKUP(backup set includes a normal backup control file), andSTANDBY(backup set includes a standby control file). | 
| INPUT_FILE_SCAN_ONLY | VARCHAR2(3) | This backup set record was created by the BACKUPVALIDATEcommand. No real backup set exists. This record is only a placeholder used to keep track of which datafiles were scanned and which corrupt blocks (if any) were found in those files. | 
| KEEP | VARCHAR2(3) | Indicates whether this backup set has a retention policy different from the value for CONFIGURERETENTIONPOLICY. Possible values areYESandNO. | 
| KEEP_OPTIONS | VARCHAR2(10) | The KEEPoptions specified for this backup set. Options can beLOGS(RMAN keeps the logs needed to recover this backup),NOLOGS(RMAN does not keep the logs needed to recover this backup), orNULL(the backup has noKEEPoptions and is subject to the default retention policy). | 
| KEEP_UNTIL | DATE | If the KEEPUNTIL TIMEclause of theBACKUPcommand was specified, then this column shows the date after which this backup becomes obsolete. If the column isNULLandKEEPOPTIONSis notNULL, the backup never becomes obsolete. |