This view lists information about RMAN persistent configuration settings. It corresponds to the V$RMAN_CONFIGURATION view.
| Column | Datatype | Description | 
|---|---|---|
| DB_KEY | NUMBER | The primary key for the target database corresponding to this configuration. Use this column to join with almost any other catalog view. | 
| CONF# | NUMBER | A unique key identifying this configuration record within the target database that owns it. | 
| NAME | VARCHAR2(65) | The type of configuration. All options of CONFIGUREcommand are valid types except:CONFIGURE EXCLUDE, (described inRC_TABLESPACE),CONFIGURE AUXNAME(described inRC_DATAFILE), andCONFIGURE SNAPSHOT CONTROLFILE(stored only in control file). | 
| VALUE | VARCHAR2(1025) | The CONFIGUREcommand setting. For example:RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS. | 
| DB_UNIQUE_NAME | VARCHAR2(512) | The DB_UNIQUE_NAMEof the database incarnation to which this record belongs. All databases in a Data Guard environment share the same DBID but differentDB_UNIQUE_NAMEvalues. The value in this column is null when the database name is not known for a specific file. For example, rows for databases managed by versions of RMAN before Oracle Database 11g are null. | 
| SITE_KEY | NUMBER | Primary key of the Data Guard database associated with this configuration. Each database in a Data Guard environment has a unique SITE_KEYvalue. You can useSITE_KEYin a join with theRC_SITEview to obtain theDB_UNIQUE_NAMEof the database. |