Conditions for Creating a Pluggable Database from Another PDB
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.)
Community Votes
100% of anonymous learners picked answer BDE. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
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.
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.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
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.