How to clone an Oracle PDB (Pluggable Database) for testing

To clone an Oracle PDB for testing, ensure prerequisites like SYSDBA privileges and source PDB availability, then use CREATE PLUGGABLE DATABASE ... FROM to create a copy within the same or another CDB, optionally using NOCOPY or FILE_NAME_CONVERT for efficiency, followed by opening the new PDB and updating configurations for test usage.

To clone an Oracle Pluggable Database (PDB) for testing, you create a copy of an existing PDB within the same or a different Container Database (CDB). This is useful for development, testing, or staging environments. The process requires proper setup and privileges but is straightforward using SQL*Plus or SQL Developer.

Prerequisites

Before cloning, ensure the following:

• You have SYSDBA or equivalent privileges on the CDB.
• The source PDB is in READ ONLY or OPEN mode.
• A new PDB name is chosen and not already in use.
• The target CDB (if different) has compatible character sets and options.
• Proper storage (file system or ASM) is available for the new data files.

Step-by-Step: Clone a PDB Locally

This example shows how to clone a PDB within the same CDB.

1. Connect to the CDB as a privileged user:
   sqlplus sys@cdb1 as sysdba
2. Ensure the source PDB is open:
   ALTER PLUGGABLE DATABASE pdb_source OPEN;
3. Issue the CREATE PLUGGABLE DATABASE ... FROM command:
   CREATE PLUGGABLE DATABASE pdb_test FROM pdb_source;
4. Open the new PDB:
   ALTER PLUGGABLE DATABASE pdb_test OPEN;
5. (Optional) Set a new admin password:
   ALTER USER pdb_admin IDENTIFIED BY new_password;

Using NOCOPY or FILE_NAME_CONVERT

By default, Oracle copies all data files. You can change this behavior:

• NOCOPY: Creates a reference without copying files (faster, but source must remain).
  Example: CREATE PLUGGABLE DATABASE pdb_test FROM pdb_source NOCOPY;
• FILE_NAME_CONVERT: Manually define file path mapping.
  Example: CREATE PLUGGABLE DATABASE pdb_test FROM pdb_source
  FILE_NAME_CONVERT = ('/pdb_source/', '/pdb_test/');

Refresh and Usage for Testing

After cloning, consider:

• Running noncdb_to_pdb.sql if the source was a non-CDB (rare in modern setups).
• Updating connection strings in test applications to point to the new PDB service.
• Verifying schema data, users, and roles are correctly copied.
• Isolating test changes—use restore points or drop the PDB after tests if needed.

Cloning a PDB is efficient and fast, especially with filesystem snapshots or storage-level clones in enterprise environments. For repeated test setups, automate the process using scripts.

Basically, just prepare the environment, run the CREATE PLUGGABLE DATABASE command, and open the new instance. It’s reliable and built into Oracle’s multitenant architecture.

The above is the detailed content of How to clone an Oracle PDB (Pluggable Database) for testing. For more information, please follow other related articles on the PHP Chinese website!