Home > SQL Developer Dialog Boxes ... > Plug In Pluggable Database
Use this dialog box to plug in a PDB. Plugging in consists of creating a PDB based on specifications in the XML file from when the original PDB was unplugged.
Database Name: Name of the PDB.
AS CLONE: Specify only if the target CDB already contains a PDB that was created using the same set of data files. The source files remain as an unplugged PDB and can be used again. Specifying AS CLONE also ensures that Oracle Database generates new identifiers, such as DBID and GUID, for the new PDB. If you specify AS CLONE, then you cannot specify the MOVE or NOCOPY clauses.
XML File Name: Specify the XML file containing the metadata for the PDB to be plugged in.
Source File Name Conversions: Determines how the database generates the names of files (such as data files and wallet files) for the PDB.
None: The database first attempts to use Oracle Managed Files to generate file names. If you are not using Oracle Managed Files, then the database uses the PDB_FILE_NAME_CONVERT initialization parameter to generate file names.
Custom Names: Select a Source Files/Target Files pair.
Custom Expressions: Specify one or more Source File Expression/Target File Expression pairs. Each pair item is a string found in names of files associated with the seed (when creating a PDB by using the seed), associated with the source PDB (when cloning a PDB), or listed in the XML file (when plugging a PDB into a CDB).
Copy Action: Determines how the database generates the names of files (such as data files and wallet files) for the PDB.
Nocopy: The files for the PDB remain in their current locations. Use this option if there is no need to copy or move the files required to plug in the PDB.
Copy: The files listed in the XML file are copied to the new location and used for the new PDB. You can also specify Source File Names Conversions to use pattern replacement in the new file names.
Move: The files listed in the XML file are moved, rather than copied, to the new location and used for the new PDB. You can also specify Source File Names Conversions to use pattern replacement in the new file names.
Storage: You can specify storage limits for the PDB total size or temporary tablespace usage, or both; or unlimited storage for either or both.
Related Topics