The CATDB12c database contains an Oracle Database version 12c catalog schema owned by the RC12C user. The RCAT11 database contains an Oracle Database version 11g catalog schema owned by the RC11…

The correct answer is A. All databases registered in the RC11 catalog are registered in the RC12C catalog. C. Local and global stored scripts that have the same name as existing scripts in the RC12C catalog. C: Stored scripts are either global or local. It is possible for global scripts, but not local scripts, to have name conflicts during import because the destination schema contains an object with the same name. In this case, RMAN renames the global script name to COPY OF…

Using RMAN for Backup and Recovery

Question

The CATDB12c database contains an Oracle Database version 12c catalog schema owned by the RC12C user. The RCAT11 database contains an Oracle Database version 11g catalog schema owned by the RC11 user in which several databases are registered. Both databases are open. You execute the RMAN commands: Which two tasks are performed as part of the import?

Options

AAll databases registered in the RC11 catalog are registered in the RC12C catalog.
BDatabases from the RC12C catalog are implicitly unregistered if the RC11 catalog has registered
CLocal and global stored scripts that have the same name as existing scripts in the RC12C catalog
DImported databases are unregistered from the RC11 catalog.
ERecovery catalog is resynchronized with the control files of the registered databases.

How the community answered

(54 responses)

A
85% (46)
B
2% (1)
D
4% (2)
E
9% (5)

Explanation

C: Stored scripts are either global or local. It is possible for global scripts, but not local scripts, to have name conflicts during import because the destination schema contains an object with the same name. In this case, RMAN renames the global script name to COPY OF script_name. Incorrect Answers: B: Ensure that the same database is not registered in both the source recovery catalog schema and destination catalog schema. If a database is registered in both schemas, then UNREGISTER this database from source recovery catalog and execute the IMPORT command again. Note: Use the IMPORT CATALOG command to import the metadata from one recovery catalog schema into a different catalog schema. If you created catalog schemas of different versions to store metadata for multiple target databases, then this command enables you to maintain a single catalog schema for all databases.

Topics

#recovery catalog import#catalog merge#stored scripts#RMAN catalog

Community Discussion

Marisol N.Apr 8, 2026

Resync with control files is baked into the import process, going with E.

Dragan P.Apr 9, 2026

Marisol, resync with the control file is a manual step you have to trigger separately, it does not happen automatically during import, so E does not hold up there. A and C cover the actual behaviors that are baked in, which is why Oracle has documented that distinction in MOS since at least the 10g days.

Samuel O.Apr 11, 2026

I keep coming back to D because when you run that IMPORT CATALOG command the whole point is migration, and Oracle does not leave a ghost copy sitting in the old 11g catalog after the move, it cleans house by unregistering those databases from RC11 so you are not managing duplicate registrations across two separate catalogs. Paired with A, because the registered databases obviously have to land somewhere and that somewhere is the RC12C catalog, which is exactly what the import operation is designed to accomplish.

Dragan P.Apr 12, 2026

Samuel, you got A right but flipped the source catalog behavior. IMPORT CATALOG copies the metadata into RC12C but leaves the old RC11 catalog completely untouched, so those databases remain registered there until you manually unregister them, which is why C is the correct second piece, not D.

Full 1Z0-063 Practice