Virtual Catalog in Oracle 18.104.22.168 and the Recovery_catalog_user Role
(Doc ID 2125233.1)
Last updated on OCTOBER 27, 2019
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 to 126.96.36.199 [Release 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Target Database Name: CDBPRODS
Catalog Tablespace: RMAN
RMAN schema: RMAN
VPC User: VPC1
As per Oracle 188.8.131.52 documentation Creating and Managing Virtual Private Catalogs with Oracle Database 12c Release 1 (184.108.40.206):
It is required to grant RECOVERY_CATALOG_OWNER to a virtual private catalog (VPC) user. This increases vulnerability, as the VPC user will have full access to base recovery catalog. In Oracle 220.127.116.11, a new role has been introduced, RECOVERY_CATALOG_USER, which should to be granted to VPC user. Through this role, the VPC user can perform basic operations like register, unregister resync catalog etc.
In version 18.104.22.168, RECOVERY_CATALOG_USER role is not their
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document