This section provides information about creating a new PDB by plugging in an unplugged PDB using EM Express.
Note:
Before you plug an unplugged PDB into a CDB:
The target CDB (the CDB that you want to plug the unplugged PDB into) must exist, and EM Express must be configured to access the CDB.
The target CDB must be in read/write mode.
The XML file that describes the unplugged PDB and the other files associated with the unplugged PDB, such as the data files, must exist and must be readable.
The target host user must be the owner of the Oracle home that the CDB (into which you want to plug the unplugged PDB) belongs to.
The platforms of the source CDB host (the host on which the CDB that previously contained the unplugged PDB is installed) and the target CDB host (the host on which the target CDB is installed) must have the same endianness, and must have the same set of database options installed.
The CDB that contained the unplugged PDB and the target CDB must have compatible character sets and national character sets. To be compatible, the character sets and national character sets must meet all the requirements specified in Oracle Database Globalization Support Guide.
To plug an unplugged PDB into a CDB:
In EM Express, navigate to the Containers page for the CDB that you want to plug the unplugged PDB into.
For more information, see "Accessing the Containers Page."
In the Containers section of the Containers page, choose Plug from the Actions menu. The Plug wizard appears.
On the General page of the Plug wizard, supply values for these fields:
Metadata File: Enter the full path to the metadata XML file that was created when the PDB was unplugged.
Reuse PDB name from Metadata File: Select this option, or disable it and specify an new name to use for the unplugged PDB when it is plugged into the CDB.
Reuse source datafile location from Metadata File: Select this option, or disable it and specify a new source datafile location to use for the unplugged PDB when it is plugged into the CDB.
Click the right arrow button to go to the Storage page.
On the Storage page, select the type of location where you want to store the datafiles for the PDB:
If the target CDB (into which you are plugging the unplugged PDB) is enabled with Oracle Managed Files and you want to use the same, then select Use Oracle Managed Files (OMF).
If the target CDB does not use OMF, then specify a datafile location or accept the default specified in the Datafile Location field.
Also on the Storage page, choose whether or not to enable unlimited storage for the datafiles.
If you do not enable unlimited storage, then you must specify values for these fields:
Max Size: The amount of storage that can be used by all tablespaces that belong to the PDB.
Max Shared Temp Size: The amount of storage in the default temporary tablespace shared by all PDBs that can be used by sessions connected to the PDB.
If no values are specified for these fields, then their values will be set to unlimited when the PDB is plugged in.
If the CDB has a current active resource plan, the Resource Limits page appears.
Supply values for these fields, or keep the default values for the PDB you are plugging in:
Shares: Assign a new share value for this PDB, or keep the current value.
CPU Utilization Limit (%): Assign a new CPU utilization percentage value for this PDB, or keep the current value.
Parallel Server Limit (%): Assign a new parallel server utilization percentage value for this PDB, or keep the current value.
Click OK.
The unplugged PDB is plugged into the CDB and is opened in read/write mode. EM Express adds the PDB to the list of containers that appears in the Containers section on the Containers page.
After configuring an HTTPS port for EM Express for this PDB, the PDB can be managed using EM Express. Administrative users who have been granted the EM_EXPRESS_ALL
role in a PDB can use EM Express to manage the PDB.
See Also:
"Configuring the HTTPS Port for EM Express" for information on configuring an HTTPS port for EM Express for a PDB
"Unplugging a PDB" for information on unplugging a PDB from a CDB