Conditions for Creating a Pluggable Database from Another PDB

1Z0-078 By islever Editorial Last updated

Create and administer RAC databases

Short answer

BDE The source PDB must be open (READ ONLY if no archive log), executed by a privileged common user in the root, and use OMF or file name conversion.

Question

Examine this command: SQL> CREATE PLUGGABLE DATABASE pdb3 FROM pdb1; Which three conditions must be true for successful execution of this command on a RAC database? (Choose three.)
  1. The source PDB must be closed on the CDB instance from where the command is executed.
  2. The source PDB must be in READ ONLY mode on all CDB instances if the CDB is in No Archive mode. Correct Answer
  3. The source PDB must use a global temporary tablespace.
  4. It can be executed only by a common user with the CREATE PLUGGABLE DATABASE system privilege connected to the root container. Correct Answer
  5. Oracle Managed Files must be enabled or PDB_FILE_NAME_CONVERT must be set. Correct Answer

Key Takeaways

The exam tests knowledge of PDB cloning requirements, specifically targeting the trap where candidates might assume the source must be closed or use temporary tablespaces, whereas it actually requires read-only access and proper file management settings.

This question examines the prerequisites for cloning a pluggable database (PDB) in an Oracle RAC environment using the CREATE PLUGGABLE DATABASE command. It establishes that specific privilege, file naming, and mode conditions must be met for successful execution.

Common mistake: Candidates often incorrectly select option A, believing the source PDB must be closed to prevent conflicts during cloning. In reality, the source must remain open (in READ ONLY mode if not archived) to allow consistent data extraction.

Expert Analysis

Why the Answer Is Correct

Option B is correct because when cloning a PDB, the source must be accessible and consistent. If the CDB is in NOARCHIVELOG mode, the source PDB must be opened in READ ONLY mode on all instances to ensure a consistent read across the cluster. Option D is correct because creating a PDB is a privileged operation that must be performed by a common user with the CREATE PLUGGABLE DATABASE system privilege connected to the root container (CDB$ROOT). Option E is correct because Oracle Managed Files (OMF) simplifies file creation; if OMF is not enabled, the PDB_FILE_NAME_CONVERT parameter must be set to map source file names to destination locations, ensuring new files are created correctly.

Why the Other Options Are Wrong

Option A is incorrect because the source PDB cannot be closed; it must be open (either READ WRITE or READ ONLY) to provide the data files for cloning. Option C is incorrect because the type of tablespace (global temporary vs. permanent) used by the source PDB does not affect the ability to clone it; temporary tablespaces are recreated upon opening the target PDB anyway.

Community Comment Notes

The community consensus strongly supports options B, D, and E. As one commenter noted, "A is incorrect, documentation states: The source PDB cannot be closed." Another user confirmed that BDE is the correct combination, aligning with official Oracle documentation which specifies the READ ONLY requirement for non-archived databases and the necessity of file conversion mechanisms.

Exam Strategy

When dealing with PDB cloning questions, always check the state of the source PDB (must be open) and the privileges required (common user in root). Remember that file naming can be handled either by OMF or explicit conversion parameters.

Frequently Asked Questions

Why can't the source PDB be closed?

The source PDB must be open to provide the data files for cloning. Closing it would make the data inaccessible for the create process.

Does the source PDB need to be in restricted mode?

No, restricted mode is not required. The key requirement is READ ONLY mode if the CDB is not in ARCHIVELOG mode to ensure consistency.

More 1Z0-078 FAQ →

Community Votes

BDE
100%

100% of anonymous learners picked answer BDE. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 3

  1. xRodge 👍 1
    The given answer is incorrect. BDE is correct. A is incorrect, documentation states: "The source PDB cannot be closed." C is incorrect, as the TEMP tablespace does not matter to this operation F is incorrect, as it would be insane to require a production DB to be in restricted mode in order to clone it. From documentation: B: "If the CDB is not in ARCHIVELOG mode, then the source PDB must be in open read-only mode. This requirement does not apply if the CDB is in ARCHIVELOG mode." D: "The current user must have the CREATE PLUGGABLE DATABASE system privilege in both the root and the source PDB." E: "Either Oracle Managed Files is enabled, or the PDB_FILE_NAME_CONVERT initialization parameter is set." Reference: https://docs.oracle.com/en/database/oracle/oracle-database/19/multi/cloning-a-pdb.html
  2. TrinhLK 👍 1
    BDE is correct
  3. 217972f 👍 1
    Sure of BDE

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Which Three Resources Use Global Concurrency Control in 19c RAC?

S-grade

Which Task Must Precede OPatch Patching of Grid Infrastructure 19c?

S-grade

What Does opatch apply Do in a Four-Node RAC Cluster?

S-grade

ACFS Encryption True Statements

S-grade

← Back to 1Z0-078 Study Guide