You are in the process of creating a Virtual Private Catalog (VPC) in your Oracle Database l1g database .The PROD1, PROD2, and PROD3 Oracle Database 10g databases are registered in the base recovery…

Anjali D.Mar 29, 2026

The answer here is A, and once you understand what a VPC is for, it clicks pretty fast. The whole point of creating a virtual catalog in 11g RMAN is precisely to support older, pre-11g clients like those 10g databases, so the fact that PROD1 and PROD2 are 10g is not a problem at all, it is actually the use case the feature was built for. The vpc1 user calling catowner.dbms_rcvcat.create_virtual_catalog is fine because the schema is explicitly qualified in the call, so vpc1 does not need to own the package or connect as CATOWNER. You also do not need a target connection to build the virtual catalog structure, that work happens entirely within the catalog database. A few people in our group initially leaned toward C, but the schema-qualified syntax is the key detail that rules it out. Anyone else want to weigh in on whether the GRANT syntax here is also worth memorizing for the exam?

Bao N.Mar 24, 2026

Took me two tries on this one. The GRANT CATALOG FOR DATABASE syntax is the 11g way of scoping catalog access to specific databases for a VPC user, and once vpc1 has those grants, connecting as vpc1 and running catowner.dbms_rcvcat.create_virtual_catalog is exactly the right sequence, you do not need to be CATOWNER to call that package as long as you have execute privileges on it. The key thing people miss is that A says "pre-Oracle 11g clients" and that is the whole point of a VPC, it lets older 10g RMAN clients connect through a subset catalog without seeing the full base catalog. The PROD1 and PROD2 being 10g databases is not a problem, it is actually the use case VPC was designed for. Genuine question for anyone who has drilled this deeper: does vpc1 need explicit EXECUTE privilege granted on dbms_rcvcat separately, or does the GRANT CATALOG FOR DATABASE implicitly cover that? I always assumed the latter but I have never confirmed it cleanly in the docs.

Lena V.Apr 17, 2026

The EXEC syntax trips people up here, but A is right, vpc1 can run that proc.

Carlos M.Apr 7, 2026

C tripped me up the first time because calling catowner.dbms_rcvcat.create_virtual_catalog while connected as vpc1 looks like it should fail, but the GRANT CATALOG FOR DATABASE command already hands vpc1 the execute privilege on that package, so the schema-qualified call works fine without switching to CATOWNER. The whole point of a Virtual Private Catalog is to give pre-11g clients like those 10g databases a segmented view of the base catalog, so B is a trap because the 10g databases being registered there is not a problem, it is literally the use case. D makes no sense in context since you are setting up the VPC structure in the catalog database, not doing a backup or restore operation that would require a target connection. Answer is A, the commands succeed and vpc1 now owns a VPC scoped to prod1 and prod2 for those older clients.

Brenda K.Apr 4, 2026

Quick win here if you know the VPC setup rules, maybe 90 seconds max so do not flag this one. The create_virtual_catalog procedure is designed exactly for this scenario, where pre-11g clients need their own catalog view, and vpc1 has been granted the right databases, so the commands run clean and A is your answer. My question is, do you understand why vpc1 can call catowner.dbms_rcvcat.create_virtual_catalog without being CATOWNER, meaning what privilege makes that cross-schema exec work after the GRANT CATALOG step?