Oracle OCP 1Z0-050（35题）解析
QUESTION 35:
Which statement is true regarding virtual private catalogs?
A. A virtual private catalog owner can create a local stored script, and have read/write access to a global stored script.
B. The virtual private catalog owner cannot create and modify the stored scripts.
C. The set of views and synonyms that make up the virtual private catalog is stored in the schema of the RMAN recovery catalog owner.
D. To perform most of the RMAN operations, the virtual catalog owner must have the SYSDBA or SYSOPER privilege on the target database.
Answer: D
解析：
完成大多数RMAN操作，虚拟目录在目标库上必须有SYSDBA权限或者SYSOPER权限。
参考Oracle官方文档：
https://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmcatdb.htm#BRADV89656
About Virtual Private Catalogs
By default, all of the users of an RMAN recovery catalog have full privileges to insert, update, and delete any metadata in the catalog. For example, if the administrators of two unrelated databases share the same recovery catalog, each administrator could, whether inadvertently or maliciously, destroy catalog data for the other's database. In many enterprises, this situation is tolerated because the same people manage many different databases and also manage the recovery catalog. But in other enterprises where clear separation of duty exists between administrators of various databases, and between the DBA and the administrator of the recovery catalog, you may desire to restrict each database administrator to modify only backup metadata belonging to those databases that they are responsible for, while still keeping the benefits of a single, centrally-managed, RMAN recovery catalog. This goal can be achieved by implementing virtual private catalogs.
Every 11g recovery catalog supports virtual private catalogs, but they are not used unless explicitly created. There is no restriction to the number of virtual private catalogs that can created beneath one recovery catalog. Each virtual private catalog is owned by a database schema user which is different than the user who owns the recovery catalog.
After creating one or more virtual private catalogs, using the directions that follow, the administrator for the recovery catalog grants each virtual private catalog the privilege to use that catalog for one or more databases that are currently registered in the recovery catalog. The administrator of the recovery catalog can also grant the privilege to register new databases while using a virtual private catalog.
Note:
Every virtual private catalog has access to all global stored scripts and those non-global stored scripts that belong to those databases for which this virtual private catalog has privileges. Virtual private catalogs cannot access non-global stored scripts that belong to databases that they do not have privileges for, and they cannot create global stored scripts.
The basic steps for creating a virtual private catalog are as follows:
-
Create the database user who will own the virtual private catalog (if this user does not exist) and grant this user access privileges.
This task is described in "Creating and Granting Privileges to a Virtual Private Catalog Owner".
-
Create the virtual private catalog.
This task is described in "Creating a Virtual Private Catalog".
After the virtual private catalog is created, you can revoke catalog access privileges as necessary. This task is described in "Revoking Privileges from a Virtual Private Catalog Owner". "Dropping a Virtual Private Catalog" explains how to drop a virtual private catalog.
If the recovery catalog is a virtual private catalog, then the RMAN client connecting to it must be at patch level 10.1.0.6 or 10.2.0.3. Oracle9i RMAN clients cannot connect to a virtual private catalog. This version restriction does not affect RMAN client connections to an Oracle Database 11g base recovery catalog, even if it has some virtual private catalog users.