To 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 the databases are…

Question

Options

• ADatabases from the RC12C catalog are implicitly unregistered if the RC11 catalog has
• BRecovery catalog is resynchronized with the control files of the registered databases.
• CImported databases are unregistered from the RC11 catalog.
• DLocal and global stored scripts that have the same name as existing scripts in the RC12C
• EAll databases registered in the RC11 catalog are registered in the RC12C catalog.

• A
  17% (10)
• B
  7% (4)
• C
  5% (3)
• D
  71% (42)

Explanation

When executing IMPORT CATALOG from the RC11 source catalog into the RC12C target catalog, Oracle registers all databases from the source into the destination catalog (E), and handles naming conflicts by renaming imported scripts that collide with existing RC12C script names rather than overwriting them (D - the full option text almost certainly ends with something like "are renamed during import").

Why the distractors are wrong:

• A is wrong - IMPORT CATALOG never implicitly unregisters databases already in the target (RC12C) catalog.
• B is wrong - catalog resynchronization with control files is a separate operation (RESYNC CATALOG) and is not triggered by an import.
• C is wrong - the source catalog (RC11) databases are not automatically unregistered; you must do that manually afterward (or use a specific clause if available in your version).

Memory tip: Think of IMPORT CATALOG as a one-way merge - it adds everything from the source into the target (all registrations flow in, scripts get renamed on conflict), but it never cleans up either catalog automatically. Nothing is deleted or synced as a side effect.

No community discussion yet for this question.