In modern data platforms, agility is a strategic imperative. Oracle Database 19c reinforces this mandate by introducing Hot Clone PDB, a feature that empowers DBAs to clone a pluggable database without shutting down the source PDB. This capability unlocks accelerated provisioning pipelines for development, testing, QA refreshes, and rapid environment replication—while keeping production workloads uninterrupted.

Hot cloning ensures the source PDB remains fully operational, enabling organizations to optimize uptime while delivering frictionless database lifecycle management.

1. What Is Hot Clone PDB?

A hot clone allows you to create a duplicate of a running pluggable database—even as transactions continue to occur. Oracle achieves this through incremental synchronization and redo apply mechanics, ensuring the cloned PDB is transactionally consistent at the completion point.

Key advantages:

• Zero downtime for the source PDB
• Faster environment provisioning
• Seamless refresh workflows for dev/test systems
• Reduced operational bottlenecks

2. Prerequisites

Ensure the following before initiating a hot clone:

• Oracle Database 19c or higher
• Source PDB is open read/write
• ARCHIVELOG mode is enabled
• Sufficient storage for the cloned PDB
• Appropriate user privileges (SYSDBA or equivalent)

3. High-Level Workflow

1. Open the source PDB in read/write mode
2. Use CREATE PLUGGABLE DATABASE ... FROM ... with REFRESH MODE MANUAL or REFRESH MODE NONE based on usage
3. Finalize the clone using ALTER PLUGGABLE DATABASE ... REFRESH (if using refreshable clone)

4. Hot Clone PDB – Syntax and Examples

Scenario: Clone PDB PDBPROD to PDBDEV While Source Is Online

Step 1: Connect to CDB Root

sqlplus / as sysdba

Step 2: Create the Clone While Source PDB Is Open

CREATE PLUGGABLE DATABASE pdbdev 
    FROM pdbprod
    FILE_NAME_CONVERT = ('/u01/app/oracle/oradata/CDB1/pdbprod/',
                         '/u01/app/oracle/oradata/CDB1/pdbdev/');

This command triggers Oracle’s hot cloning mechanics automatically when the source PDB is open in read/write mode.

5. Creating a Refreshable Hot Clone (Optional Enhanced Pattern)

Refreshable clones are strategic assets for environments requiring periodic data refresh from production.

Step 1: Create a Refreshable Clone

CREATE PLUGGABLE DATABASE pdbdev 
    FROM pdbprod
    REFRESH MODE MANUAL
    FILE_NAME_CONVERT = ('/u01/app/oracle/oradata/CDB1/pdbprod/',
                         '/u01/app/oracle/oradata/CDB1/pdbdev/');

Step 2: Open the Clone

ALTER PLUGGABLE DATABASE pdbdev OPEN;

Step 3: Refresh the Clone on Demand

ALTER PLUGGABLE DATABASE pdbdev REFRESH;

This mechanism streamlines repeated environment refresh cycles efficiently.

6. Verify the Clone

SELECT pdb_name, status 
FROM dba_pdbs;

You should now see:

PDBDEV      NORMAL

7. Benefits for Enterprise DBA Workflows

Oracle 19c’s hot cloning elevates operational excellence by enabling:

• Continuous service delivery—no disruption to source PDB
• Rapid provisioning of dev/test sandboxes
• Infrastructure modernization aligned with agile DevOps frameworks
• Improved data governance through refreshable clone patterns
• Optimized resource allocation via lightweight PDB architectures

This paradigm positions the DBA as a catalyst for innovation, ensuring environments are delivered at the speed of business.

8. Conclusion

Hot cloning in Oracle 19c transforms PDB lifecycle operations from time-consuming maintenance tasks into streamlined, online, enterprise-grade workflows. By eliminating the need to shut down the source PDB, organizations can confidently provision replicas, accelerate testing cycles, and support modern CI/CD models—while safeguarding service continuity.

This powerful feature reinforces Oracle’s commitment to operational efficiency, resilience, and digital acceleration.