5.50 RC_RMAN_BACKUP_SUBJOB_DETAILS

RC_RMAN_BACKUP_SUBJOB_DETAILS provides details for groups of similar operations within an RMAN session.

This view is primarily intended to be used internally by Enterprise Manager.

Column Data Type Description

DB_KEY

NUMBER

The primary key for this database.

DB_NAME

VARCHAR2(8)

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

SESSION_KEY

NUMBER

Session identifier. Use in joins with RC_RMAN_OUTPUT and RC_RMAN_BACKUP_JOB_DETAILS.

SESSION_RECID

NUMBER

With SESSION_KEY and SESSION_STAMP, used to uniquely identify the job output from RC_RMAN_OUTPUT.

SESSION_STAMP

NUMBER

With SESSION_RECID and SESSION_KEY, used to uniquely identify the job output from RC_RMAN_OUTPUT.

OPERATION

VARCHAR2(33)

The possible values are BACKUP, ROLLFORWARD, VALIDATE, or BACKUPSET. For each operation type in a session, the view contains one row with each value representing all operations of that type during the session.

COMMAND_ID

VARCHAR2(33)

Either a user-specified value set using SET COMMAND ID, or an RMAN-generated unique command id.

START_TIME

DATE

Start time of the first backup command in the job

END_TIME

DATE

End time of the last backup job in the job.

INPUT_BYTES

NUMBER

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

OUTPUT_BYTES

NUMBER

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

STATUS_WEIGHT

NUMBER

Used internally by Enterprise Manager.

OPTIMIZED_WEIGHT

NUMBER

Used internally by Enterprise Manager.

INPUT_TYPE_WEIGHT

NUMBER

Used internally by Enterprise Manager.

OUTPUT_DEVICE_TYPE

VARCHAR2(17)

Type of output device: DISK, SBT_TAPE, or *. An asterisk (*) indicates a backup job that wrote its output to multiple device types.

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.

AUTOBACKUP_DONE

VARCHAR2(3)

'Whether a control file autobackup was done as part of this job (YES) or not done (NO).

STATUS

VARCHAR2(23)

One of the following values: RUNNING,RUNNING WITH WARNINGS, RUNNING WITH ERRORS, COMPLETED, COMPLETED WITH WARNINGS, COMPLETED WITH ERRORS, FAILED.

INPUT_TYPE

VARCHAR2(13)

Contains one of the following values: DATABASE FULL, RECOVERY AREA, DATABASE INCR, DATAFILE FULL, DATAFILE INCR, ARCHIVELOG, CONTROLFILE, SPFILE.

If a subjob includes backups corresponding to multiple values, then multiple rows appear in the view, corresponding to the different INPUT_TYPE values for each type of input, with corresponding values for the INPUT_BYTES, OUTPUT_BYTES, INPUT_BYTES_DISPLAY, OUTPUT_BYTES_DISPLAY fields.

OPTIMIZED

VARCHAR2(3)

If the value of the OPERATION column is BACKUP, then OPTIMIZED is YES or NO, depending on whether backup optimization was applied.

AUTOBACKUP_COUNT

NUMBER

Number of autobackups performed by this job.

COMPRESSION_RATIO

NUMBER

Compression ratio for this backup.

INPUT_BYTES_DISPLAY

VARCHAR2(32K)

Same value as 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 for example, 798.01M or 5.25G.