5.16 RC_BACKUP_PIECE_DETAILS
RC_BACKUP_PIECE_DETAILS contains detailed information about all available backup pieces recorded in the recovery catalog.
The semantics of most columns duplicate the RC_BACKUP_PIECE recovery catalog view. This view is primarily intended to be used internally by Enterprise Manager.
| Column | Data Type | Description |
|---|---|---|
|
|
|
Session identifier. Use in joins with |
|
|
|
With |
|
|
|
With |
|
|
|
The |
|
|
|
The primary key for this database in the recovery catalog. Use this column to join with almost any other catalog view. |
|
|
|
The DBID of the database incarnation to which this record belongs. |
|
|
|
The primary key for the backup piece in the recovery catalog. If you issue the |
|
|
|
The backup piece |
|
|
|
The backup piece stamp propagated from |
|
|
|
The primary key of the backup set to which this record belongs in the recovery catalog. Use this column to join with |
|
|
|
The |
|
|
|
The |
|
|
|
The type of backup. Possible values are |
|
|
|
For incremental backups, indicates the level of incremental backup. Possible values are |
|
|
|
The number of the backup piece. The first piece has the value of 1. |
|
|
|
Indicates the copy number for backup pieces created with duplex enabled. 1 if the backup piece is not duplexed. |
|
|
|
Type of the device on which the backup piece resides. Set to |
|
|
|
The file name of the backup piece. |
|
|
|
Comments about the backup piece. |
|
|
|
A comment that contains further information about the media manager that created this backup. |
|
|
|
The number of the media pool in which the backup is stored. |
|
|
|
Specifies whether backup media supports concurrent access: |
|
|
|
The tag associated with this backup piece. |
|
|
|
The time when RMAN started to write the backup piece. |
|
|
|
The time when the backup piece was completed. |
|
|
|
The duration of the creation of the backup piece. |
|
|
|
The status of the backup piece: |
|
|
|
The size of the backup piece in bytes. |
|
|
|
|
|
|
|
Unique key for the row in |
|
|
|
|
|
|
|
Primary key of the Data Guard database associated with this file. Each database in a Data Guard environment has a unique |
|
|
|
Indicates whether the backup piece is encrypted ( |
|
|
|
Indicates whether the backup piece is backed up to Oracle Secure Backup ( 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. |
|
|
|
Number of backup pieces in the backup set containing this backup piece. |
|
|
|
Same value as |