5.19 RC_BACKUP_SET_DETAILS

RC_BACKUP_SET_DETAILS provides details about currently available backup sets, including backup sets created by the use of the BACKUP BACKUPSET command.

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_OUTPUT and RC_RMAN_BACKUP_JOB_DETAILS.

SESSION_RECID

NUMBER

With SESSION_STAMP, uniquely identifies output for this backup job from RC_RMAN_OUTPUT.

SESSION_STAMP

NUMBER

With SESSION_RECID, uniquely identifies output for this backup job from RC_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_NAME of the database incarnation to which this record belongs.

BS_KEY

NUMBER

The primary key of the backup set to which this record belongs in the recovery catalog. Use this column to join with RC_BACKUP_SET or RC_BACKUP_PIECE.

RECID

NUMBER

The backup set RECID and STAMP form a concatenated primary key that uniquely identifies this record in the target database control file.

STAMP

NUMBER

The backup set RECID and STAMP form a concatenated primary key that uniquely identifies this record in the target database control file.

SET_STAMP

NUMBER

The SET_STAMP value from V$BACKUP_SET. SET_STAMP and SET_COUNT form a concatenated key that uniquely identifies this record in the target database control file.

SET_COUNT

NUMBER

The SET_COUNT value from V$BACKUP_SET. SET_STAMP and SET_COUNT form a concatenated key that uniquely identifies this record in the target database control file.

BACKUP_TYPE

VARCHAR2(1)

The type of the backup: D (full backup), I ( level 0 incremental or level 1 incremental), L (archived redo log).

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), and STANDBY (backup set includes a standby control file).

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.

BLOCK_SIZE

VARCHAR2

The block size used when creating the backup pieces in the backup set.

KEEP

VARCHAR2(3)

Indicates whether this backup set 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 BACKUP command was specified, then this column shows the date after which this backup becomes obsolete. If the column is NULL and KEEP OPTIONS is not NULL, the backup never becomes obsolete.

KEEP_OPTIONS

VARCHAR2(11)

The KEEP options specified for this backup set. Possible values are NOLOGS, BACKUP_LOGS, LOGS, and NULL. NOLOGS indicates a consistent backup made when the database was mounted. BACKUP_LOGS indicates that the backup was made in open mode, so archived log backups must be applied to make it consistent. LOGS indicates a long-term backup made with the LOGS keyword, which is now deprecated. NULL indicates that this backup has no KEEP options and becomes obsolete based on the retention policy.

DEVICE_TYPE

VARCHAR2(255)

Device type on which the backup is stored. If the backup set is stored on multiple types of devices (for example, if a backup set on disk is also backed up to tape using BACKUP BACKUPSET), then this column contains an asterisk (*). Values are DISK or SBT_TAPE.

COMPRESSED

VARCHAR2(3)

YES if RMAN's binary compression was used in creating the backup set. NO, otherwise.

NUM_COPIES

NUMBER

Number of identical copies of this backup set created during the backup, for example if duplexing was used.

OUTPUT_BYTES

NUMBER

Sum of sizes of all output pieces generated by this job.

ORIGINAL_INPUT_BYTES

NUMBER

Sum of sizes of all input files backed up for this job.

COMPRESSION_RATIO

NUMBER

Compression ratio for this backup.

STATUS

CHAR(1)

The status of the backup set: always A (all backup pieces available), because this view only reflects available backup sets.

ORIGINAL_INPRATE_BYTES

NUMBER

Number of bytes read each second when the backup set was initially created.

OUTPUT_RATE_BYTES

NUMBER

Number of bytes written each second when the backup set was initially created.

ORIGINAL_INPUT_BYTES_DISPLAY

VARCHAR2(32K)

Same value as ORIGINAL_INPUT_BYTES, but converted to a user-displayable format, for example, 798.01M or 5.25G.

OUTPUT_BYTES_DISPLAY

VARCHAR2(32K)

Same value as OUTPUT_BYTES, but converted to a user-displayable format, for example, 798.01M or 5.25G.

ORIGINAL_INPRATE_BYTES_DISPLAY

VARCHAR2(32K)

Same value as ORIGINAL_INPRATE_BYTES, but converted to a user-displayable format, for example, 798.01M or 5.25G.

OUTPUT_RATE_BYTES_DISPLAY

VARCHAR2(32K)

Same value as OUTPUT_RATE_BYTES, but converted to a user-displayable format, for example, 798.01M or 5.25G.

TIME_TAKEN_DISPLAY

VARCHAR2(32K)

Same value as ELAPSED_SECONDS, but converted to a user-displayable format in hours, minutes and seconds.

ENCRYPTED

VARCHAR2(3)

Indicates whether the backup piece is encrypted (YES) or not (NO).

BACKED_BY_OSB

VARCHAR2(3)

Indicates whether the backup piece is backed up to Oracle Secure Backup (YES) or not (NO).

Note:

Oracle Secure Backup (OSB) 19.1 desupport was announced on May 1, 2026 with premier support end date on September 30, 2027. See My Oracle Support note PNEWS3035 for more information. Please refer to Lifetime Support Policy: Oracle Technology Products for updated support timeframes.

Oracle recommends that database backups to cloud take advantage of Oracle Database Zero Data Loss Cloud Protect, which uses Oracle Zero Data Loss Autonomous Recovery Service in OCI. Cloud Protect offers an efficient incremental forever backup strategy, real-time transaction protection, logically air-gapped immutable backups, and fast, point-in-time recovery.

For customers who require database backups to Amazon S3, Oracle Database Cloud Backup for Amazon S3 may be used. This offering is similar to Oracle Secure Backup Cloud Module in that it is fully integrated with Recovery Manager (RMAN) and enables you to back up your Oracle database to Amazon S3. You can exchange your Oracle Secure Backup license for an Oracle Database Cloud Backup for Amazon S3 license on a 1:1 basis. See Oracle Database Cloud Backup for Amazon S3 for more information.