Clone a Pluggable Database Manually

Clone a Pluggable Database (PDB) Manually

Cloning an existing local PDB is similar to creating a new PDB from the seed PDB, except now we are using non-seed PDB as the source, which we have to identify using the FROM clause. Make sure the source PDB is open in READ ONLY mode.

ALTER PLUGGABLE DATABASE pdb3 CLOSE;

ALTER PLUGGABLE DATABASE pdb3 OPEN READ ONLY;

CREATE PLUGGABLE DATABASE pdb4 FROM pdb3

  FILE_NAME_CONVERT=('/u01/app/oracle/oradata/cdb1/pdb3/','/u01/app/oracle/oradata/cdb1/pdb4/');

ALTER PLUGGABLE DATABASE pdb4 OPEN READ WRITE;

-- Switch the source PDB back to read/write

ALTER PLUGGABLE DATABASE pdb3 CLOSE;

ALTER PLUGGABLE DATABASE pdb3 OPEN READ WRITE;

The cloning syntax also allows for cloning from remote databases using a database link in the local CBD. There are a few restriction associated with this functionality.

• The database link can point directly to the remote PDB or to a common user in the remote CBD that owns the remote PDB.
• If it points to a common user in the remote CBD that owns the remote PDB, that user must have the CREATE PLUGGABLE DATABASE system privilege.
• The source and target CDBs must have the same endians.
• The source and target CDBs must have the same options installed.
• The source and target CDBs must have the same character set and national character set.

Assuming the remote PDB was in READ ONLY mode, the following command should perform the required operation.

CREATE PLUGGABLE DATABASE pdb5 FROM remote_pdb5@remotecdb1

  FILE_NAME_CONVERT=('/u01/app/oracle/oradata/cdb1/remote_pdb5/','/u01/app/oracle/oradata/cdb1/pdb5/');

ALTER PLUGGABLE DATABASE pdb4 OPEN READ WRITE;

This functionality does not work properly in the 12.1.0.1 release of the database, but it has been fixed in 12.1.0.2.

Plugin a Pluggable Database (PDB) Manually

Plugin a Pluggable Database (PDB) Manually

Plugging in a PDB into the CDB is similar to creating a new PDB. First check the PBD is compatible with the CDB by calling the DBMS_PDB.CHECK_PLUG_COMPATIBILITY function, passing in the XML metadata file and the name of the PDB you want to create using it.

SET SERVEROUTPUT ON

DECLARE

  l_result BOOLEAN;

BEGIN

  l_result := DBMS_PDB.check_plug_compatibility(

                pdb_descr_file => '/u01/app/oracle/oradata/cdb1/pdb2/pdb2.xml',

                pdb_name       => 'pdb2');

  IF l_result THEN

    DBMS_OUTPUT.PUT_LINE('compatible');

  ELSE

    DBMS_OUTPUT.PUT_LINE('incompatible');

  END IF;

END;

/

compatible

PL/SQL procedure successfully completed.

SQL>

If the PDB is compatible, create a new PDB using it as the source. If we were creating it with a new name we might do something like this.

CREATE PLUGGABLE DATABASE pdb5 USING '/u01/app/oracle/oradata/cdb1/pdb2/pdb2.xml'

  FILE_NAME_CONVERT=('/u01/app/oracle/oradata/cdb1/pdb2/','/u01/app/oracle/oradata/cdb1/pdb5/');

Instead, we want to plug the database back into the same container, so we don't need to copy the files or recreate the temp file, so we can do the following.

CREATE PLUGGABLE DATABASE pdb2 USING '/u01/app/oracle/oradata/cdb1/pdb2/pdb2.xml'

  NOCOPY

  TEMPFILE REUSE;

ALTER PLUGGABLE DATABASE pdb2 OPEN READ WRITE;

SELECT name, open_mode

FROM   v$pdbs

ORDER BY name;

NAME                          OPEN_MODE

------------------------------ ----------

PDB$SEED                      READ ONLY

PDB1                          MOUNTED

PDB2                          READ WRITE

PDB3                          READ WRITE

SQL>

Create a Pluggable Database (PDB) Manually

Create a Pluggable Database (PDB) Manually

To create a new pluggable database from the seed database, all we have to do is tell Oracle where the file should be placed. We can do this using one of two methods. The first method uses theFILE_NAME_CONVERT clause in the CREATE PLUGGABLE DATABASE statement.

CONN / AS SYSDBA

CREATE PLUGGABLE DATABASE pdb2 ADMIN USER pdb_adm IDENTIFIED BY Password1

  FILE_NAME_CONVERT=('/u01/app/oracle/oradata/cdb1/pdbseed/','/u01/app/oracle/oradata/cdb1/pdb2/');

Alternatively, we can specify the PDB_FILE_NAME_CONVERT initialization parameter before calling the command without using the FILE_NAME_CONVERT clause.

CONN / AS SYSDBA

ALTER SESSION SET PDB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/cdb1/pdbseed/','/u01/app/oracle/oradata/cdb1/pdb3/';

CREATE PLUGGABLE DATABASE pdb3 ADMIN USER pdb_adm IDENTIFIED BY Password1;

Every time there is a need to convert file locations, either of these two methods will work. For the remainder of the article I will stick to using the FILE_NAME_CONVERT method to cut down on the variations I have to display.

We can see the PDBs are present by querying the DBA_PDBS and V$PDBS views.

COLUMN pdb_name FORMAT A20

SELECT pdb_name, status

FROM   dba_pdbs

ORDER BY pdb_name;

PDB_NAME            STATUS

-------------------- -------------

PDB$SEED            NORMAL

PDB1                NORMAL

PDB2                NEW

PDB3                NEW

SQL>

SELECT name, open_mode

FROM   v$pdbs

ORDER BY name;

NAME                          OPEN_MODE

------------------------------ ----------

PDB$SEED                      READ ONLY

PDB1                          MOUNTED

PDB2                          MOUNTED

PDB3                          MOUNTED

SQL>

The PDBs are created with the status of 'NEW'. They must be opened in READ WRITE mode at least once for the integration of the PDB into the CDB to be complete.

ALTER PLUGGABLE DATABASE pdb2 OPEN READ WRITE;

ALTER PLUGGABLE DATABASE pdb3 OPEN READ WRITE;

SELECT pdb_name, status

FROM   dba_pdbs

ORDER BY pdb_name;

PDB_NAME            STATUS

-------------------- -------------

PDB$SEED            NORMAL

PDB1                NORMAL

PDB2                NORMAL

PDB3                NORMAL

SQL>

SELECT name, open_mode

FROM   v$pdbs

ORDER BY name;

NAME                          OPEN_MODE

------------------------------ ----------

PDB$SEED                      READ ONLY

PDB1                          MOUNTED

PDB2                          READ WRITE

PDB3                          READ WRITE

SQL>

Note. Depending on the syntax used, you may need to grant the PDB_DBA role to the local admin users for the PDB.

Oracle PL/SQL Interview Questions       When Use ADG (Active Data Guard)

Oracle GoldenGate    Oracle Active Data Guard and Oracle GoldenGate
GO TO ORACLE Technology Network