You must migrate a non-CDB Oracle 11g Database to a CDB without first performing an upgrade to the non-CDB. User-defined objects are stored in several tablespaces in the non-CDB. Which three methods…

Question

Options

• AData Pump full database export and import
• Bcloning the non-CDB as a PDB
• Creplication using GoldenGate
• DData Pump transportable tablespaces
• EData Pump full transportable database
• Fthe DBMS_PDB package

• A
  58% (22)
• B
  5% (2)
• E
  24% (9)
• F
  13% (5)

Explanation

Migrating from Oracle 11g non-CDB to a CDB without an intermediate upgrade limits you to methods that are version-agnostic and don't require Oracle 12c features on the source side. Data Pump full export/import (A) is a classic logical migration path that works across any Oracle versions. GoldenGate replication (C) can replicate changes from an 11g source into a target PDB with minimal downtime. Transportable Tablespaces via Data Pump (D) is a physical-plus-logical method that has worked cross-version since Oracle 8i and handles the multi-tablespace requirement directly.

The distractors fail for the following reasons:

• B (Cloning non-CDB as PDB) and F (DBMS_PDB package) both require the source to already be an Oracle 12c non-CDB - they rely on 12c metadata XML descriptors that 11g cannot produce.
• E (Full Transportable Database) sounds similar to D but is incorrect here because this feature requires the source to be at minimum 11.2.0.3 with specific patches; a generic "Oracle 11g" non-CDB may not meet that requirement, and its target import path into a PDB has additional constraints.

Memory tip: Ask yourself "Does this method need 12c on the source?" - if yes (DBMS_PDB, cloning), it's out. The three correct answers (A, C, D) are all proven cross-version workhorses that have no dependency on the source version being 12c.

No community discussion yet for this question.