Migrate PDBs

Relocate or clone pluggable databases (PDBs) from a source CDB to target CDB.

The pdb command supports the following options:

Syntax

exacloudmigration pdb [-hV] [command]

Table 3-36 exacloudmigration pdb Commands

Command Description
relocate Relocates pluggable databases (PDBs) from a source CDB to target CDB.
clone Clones pluggable databases (PDBs) from a source CDB to target CDB or with in source CDB.
-h, --help Displays help information about the command and its options.
-V, --version Displays the version of the utility.

Relocate PDBs

Relocate pluggable databases (PDBs) from a source CDB to target CDB.

The pdb relocate command supports the following options:

Syntax

exacloudmigration pdb relocate [-ahV] -i <inputFile> [-w <walletFile] [-a|-l <pdbNames>] [--dry-run]

Table 3-37 exacloudmigration pdb relocate Commands

Command Description
-a, --all Relocates all pluggable databases (PDBs).
-i, --inputFile Specifies the PDB input file name with complete path.
-l, --pdbNames Specifies a comma-delimited list of PDBs to perform relocate operation.

Example:

  • To relocate a PDB: -l pdb1
  • To relocate multiple PDBs: -l pdb1,pdb2,pdb3
-w, --walletFile Specifies the wallet file name with the path.
--dry-run Performs dry run without relocating PDBs.
-h, --help Displays help information about the command and its options.
-V, --version Displays the version of the utility.

Examples:

  • To validate the PDBs input template file and perform a --dry-run:
    /home/opc>./exacloudmigration pdb relocate -a -i inputs/infra_<infra-text>/vmcluster_vmcluster1/DBNAME1_pdb_inputs -w ewallet.p12 --dry-run

    Specify the password for reading the wallet file.

  • To validate a comma-delimited list of PDBs of PDB input template file and perform a --dry-run:
    /home/opc>./exacloudmigration pdb relocate -i inputs/infra_<infra-text>/vmcluster_vmcluster1/DBNAME1_pdb_inputs -w ewallet.p12 -l PDB1,PDB2 --dry-run

    Specify the password for reading the wallet file.

  • To relocate all pluggable databases (PDBs) from a source CDB to target CDB, following successful validation and dry run:
    /home/opc>./exacloudmigration pdb relocate -a -i inputs/infra_<infra-text>/vmcluster_vmcluster1/DBNAME1_pdb_inputs -w ewallet.p12

    Specify the password for reading the wallet file.

  • To relocate comma-delimited list of pluggable databases (PDBs) from a source CDB to target CDB, following successful validation and dry run:
    /home/opc>./exacloudmigration pdb relocate -i inputs/infra_<infra-text>/vmcluster_vmcluster1/DBNAME1_pdb_inputs -w ewallet.p12 -l PDB1,PDB2

    Specify the password for reading the wallet file.

    Note:

    • If the database wallet file is not used, the command prompts for the SYS and TDE passwords for each database. If KMS is used, the TDE password is not required because key management is handled automatically by the utility.
    • If the database wallet file is used, but a password entry for any database is missing, the utility stops execution and displays an error indicating that the password does not exist in the wallet.
    • After PDB relocation, source database PDB is dropped automatically.

Clone PDBs

Clone pluggable databases (PDBs) from a source CDB to target CDB or with in source CDB.

The pdb clone command supports the following options:

Syntax

exacloudmigration pdb clone [-ahV] -i <inputFile> [-w <walletFile] [-a|-l <pdbNames>] [--dry-run]

Table 3-38 exacloudmigration pdb clone Commands

Command Description
-a, --all Clones all pluggable databases (PDBs).
-i, --inputFile Specifies the PDB input file name with complete path.
-l, --pdbNames Specifies a comma-delimited list of PDBs to perform clone operation.

Example:

  • To relocate a PDB: -l pdb1
  • To relocate multiple PDBs: -l pdb1,pdb2,pdb3
-w, --walletFile Specifies the wallet file name with the path.
--dry-run Performs dry run without cloning PDBs.
-h, --help Displays help information about the command and its options.
-V, --version Displays the version of the utility.

Examples:

  • To validate the PDBs input template file and perform a --dry-run:
    /home/opc>./exacloudmigration pdb clone -a -i inputs/infra_<infra-text>/vmcluster_vmcluster1/DBNAME1_pdb_inputs -w ewallet.p12 --dry-run

    Specify the password for reading the wallet file.

  • To validate a comma-delimited list of PDBs of PDB input template file and perform a --dry-run:
    /home/opc>./exacloudmigration pdb clone -i inputs/infra_<infra-text>/vmcluster_vmcluster1/DBNAME1_pdb_inputs -w ewallet.p12 -l PDB1,PDB2 --dry-run

    Specify the password for reading the wallet file.

  • To clone all pluggable databases (PDBs) from a source CDB to target CDB, following successful validation and dry run:
    /home/opc>./exacloudmigration pdb clone -a -i inputs/infra_<infra-text>/vmcluster_vmcluster1/DBNAME1_pdb_inputs -w ewallet.p12

    Specify the password for reading the wallet file.

  • To clone comma-delimited list of pluggable databases (PDBs) from a source CDB to target CDB, following successful validation and dry run:
    /home/opc>./exacloudmigration pdb clone -i inputs/infra_<infra-text>/vmcluster_vmcluster1/DBNAME1_pdb_inputs -w ewallet.p12 -l PDB1,PDB2

    Specify the password for reading the wallet file.

Note:

  • DB link user name and password is required, only if cloneType=REFRESH
  • If a database wallet file is not provided, the command prompts for the following credentials based on the clone type:
    • cloneType=LOCAL: TDE password only
    • cloneType=REMOTE: SYS password and TDE password
    • cloneType=REFRESH: SYS password, TDE password, and database link (DBLINK) user password
  • If the database wallet file is already generated using section (Database wallet operations) for SYS and TDE, then to add DBLink username and password to wallet file, use "edit_dbwallet" command option.
  • If the database wallet file is used, but a password entry for any database is missing, the utility stops execution and displays an error indicating that the password does not exist in the wallet.
  • For any cloneType, if KMS is used, the TDE password is not required because key management is handled automatically by the utility.