15.You are in the process of creating a virtual private catalog in your Oracle Database 11g database. The
PROD1, PROD2, and PROD3 Oracle Database 10g databases are registered in the base recovery
catalog. The database user who owns the base recovery catalog is CATOWNER. CATOWNER executes
the following command to grant privileges to a new user VPC1 using Oracle Database 11g RMAN
executables:
RMAN> GRANT CATALOG FOR DATABASE prod1, prod2 TO vpc1;
Then you issue the following commands:
RMAN> CONNECT CATALOG vpc1/oracle@catdb;
RMAN> SQL "EXEC catowner.dbms_rcvcat.create_virtual_catalog;"
What is the outcome of the above commands?
A. They execute and create a virtual catalog for pre-Oracle 11g clients.
B. They produce an error because PROD1 and PROD2 databases belong to the older version.
C. They produce an error because you need to connect as CATOWNER to execute this packaged
procedure.
D. They produce an error because you need to connect to the target database to execute this packaged
procedure.
Answer: A
答案解析:
参考:http://blog.csdn.net/rlhua/article/details/13169205
官方参考:http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta013.htm#RCMRF117
Because this operator eventually intends to use the virtual catalog with Oracle Database 10g target databases, the operator must execute theCREATE_VIRTUAL_CATALOG
PL/SQL procedure before using the virtual catalog (as explained in "Usage Notes"). In the following example, the backup operator connects to the recovery catalog database as vpc1
and executes the PL/SQL procedure as follows:
Usage Notes
Typically, you create the recovery catalog in a database created especially for this purpose. It is not recommended to create the recovery catalog in the SYS
schema.
The best practice is to create one recovery catalog that serves as the central RMAN repository for many databases. For this reason it is called the base recovery catalog.
The owner of the base recovery catalog can GRANT
or REVOKE
restricted access to the catalog to other database users. Each restricted user has full read/write access to his own metadata, which is called a virtual private catalog. The RMAN metadata is stored in the schema of the virtual private catalog owner. The owner of the base recovery catalog controls what each virtual catalog user can access.
You must take an extra step when intending to use a 10.2 or earlier release of RMAN with a virtual catalog. Before using the virtual private catalog, this user must connect to the recovery catalog database as the virtual catalog owner and execute the following PL/SQL procedure (where base_catalog_owner
is the database user who owns the base recovery catalog):
官方参考:http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta013.htm#RCMRF117
Because this operator eventually intends to use the virtual catalog with Oracle Database 10g target databases, the operator must execute theCREATE_VIRTUAL_CATALOG
PL/SQL procedure before using the virtual catalog (as explained in "Usage Notes"). In the following example, the backup operator connects to the recovery catalog database as vpc1
and executes the PL/SQL procedure as follows:
Usage Notes
Typically, you create the recovery catalog in a database created especially for this purpose. It is not recommended to create the recovery catalog in the SYS
schema.
The best practice is to create one recovery catalog that serves as the central RMAN repository for many databases. For this reason it is called the base recovery catalog.
The owner of the base recovery catalog can GRANT
or REVOKE
restricted access to the catalog to other database users. Each restricted user has full read/write access to his own metadata, which is called a virtual private catalog. The RMAN metadata is stored in the schema of the virtual private catalog owner. The owner of the base recovery catalog controls what each virtual catalog user can access.
You must take an extra step when intending to use a 10.2 or earlier release of RMAN with a virtual catalog. Before using the virtual private catalog, this user must connect to the recovery catalog database as the virtual catalog owner and execute the following PL/SQL procedure (where base_catalog_owner
is the database user who owns the base recovery catalog):