Do you want to create an application container instead of a PDB?

Specify the AS APPLICATION CONTAINER clause.

Omit the AS APPLICATION CONTAINER clause.

Creating an application container in a CDB

Are you plugging a PDB into a CDB that contains one or more PDBs that were created by plugging in the same PDB?

Specify the AS CLONE clause to ensure that Oracle Database generates a unique PDB DBID, GUID, and other identifiers expected for the new PDB. The PDB is plugged in as a clone of the unplugged PDB to ensure that all of its identifiers are unique.

Omit the AS CLONE clause.

Plugging in an unplugged PDB

Do you want to create an application seed in an application container?

Specify the AS SEED clause.

Omit the AS SEED clause.

Creating an application seed in an application container

Do you want to use a CREATE_FILE_DEST clause to specify the Oracle Managed Files default location for the PDB files?

When creating a PDB from the PDB seed or an application seed, the source files are the files associated with the seed.

Include a CREATE_FILE_DEST clause that specifies the default file system directory or Oracle ASM disk group for the PDB's files.

Omit the CREATE_FILE_DEST clause.

Use one of these techniques to specify the target locations of the files:

• FILE_NAME_CONVERT clause

• Enable Oracle Managed Files for the CDB for it to determine the target locations.

• Specify the target locations in the PDB_FILE_NAME_CONVERT initialization parameter.

See "PDB File Locations".

Creating a PDB from the PDB seed or an application seed

Cloning a PDB

Relocating a PDB

Plugging in an unplugged PDB

Do you want to specify a default permanent tablespace for the PDB?

Specify a DEFAULT TABLESPACE clause with the appropriate limits.

Oracle Database will assign to this tablespace any non-SYSTEM users for whom you do not specify a different permanent tablespace.

When creating a PDB from the PDB seed or an application seed, Oracle Database creates a smallfile tablespace and sets it as the default tablespace. When using a technique other than creation from the PDB seed or an application seed, the specified tablespace must exist in the source PDB.

Omit the DEFAULT TABLESPACE clause.

If you do not specify this clause, then the SYSTEM tablespace is the default permanent tablespace for non-SYSTEM users. Using the SYSTEM tablespace for non-SYSTEM users is not recommended.

Creating a PDB from the PDB seed or an application seed

Cloning a PDB

Relocating a PDB

Plugging in an unplugged PDB

Do you want to use a FILE_NAME_CONVERT clause to specify the target locations of the files?

When creating a PDB from the PDB seed or an application seed, the source files are the files associated with the seed.

Include a FILE_NAME_CONVERT clause that specifies the target locations of the files based on the names of the source files.

Omit the FILE_NAME_CONVERT clause.

Use one of these techniques to specify the target locations of the files:

• CREATE_FILE_DEST clause

• Enable Oracle Managed Files for the CDB for it to determine the target locations.

• Specify the target locations in the PDB_FILE_NAME_CONVERT initialization parameter.

See "PDB File Locations".

Creating a PDB from the PDB seed or an application seed

Cloning a PDB

Relocating a PDB

Creating a proxy PDB (Only applies to data files in the SYSTEM and SYSAUX tablespaces.)

Plugging in an unplugged PDB

Is the PDB a reference PDB with a dependent proxy PDB, and is the host name of its listener changing?

Include a HOST clause and specify the host name of the listener for the PDB being created.

For example, you might have a listener network for the physical host name and default port and configure a second listener bound to a virtual host name and virtual IP address with a nondefault port number.

Omit the HOST clause.

Creating a PDB from the PDB seed or an application seed

Cloning a PDB

Relocating a PDB

Plugging in an unplugged PDB

Do you want to specify the logging attribute of the tablespaces in the new PDB?

Include the logging_clause.

Omit the logging_clause.

Creating a PDB from the PDB seed or an application seed

Cloning a PDB

Plugging in an unplugged PDB

Do you want to copy or move the files to a new location?

Specify COPY to copy the files to a new location. COPY is the default. Specify MOVE to move the files to a new location. Use one of these techniques to specify the target location:

• Include a FILE_NAME_CONVERT clause that specifies the target locations based on the names of the source files.

• Include a CREATE_FILE_DEST clause that specifies the Oracle Managed Files default location for the PDB's files.

• Enable Oracle Managed Files for it to determine the target locations.

• Specify the target locations in the PDB_FILE_NAME_CONVERT initialization parameter.

See "PDB File Locations".

Specify NOCOPY.

Plugging in an unplugged PDB

Do you want to specify that the data model definition of the source PDB is cloned but not the data of the source PDB?

Include the NO DATA clause.

Omit the NO DATA clause.

Cloning a PDB

Do you want to use multiple parallel execution servers to parallelize PDB creation?

To let the CDB choose the degree of parallelism, include or omit the PARALLEL clause.

To specify the degree of parallelism, specify the PARALLEL clause with an integer. For example, specify PARALLEL 4 to indicate a degree of parallelism of 4.

Creating a PDB from the PDB seed or an application seed

Cloning a PDB

Do you want to use a PATH_PREFIX clause to restrict file paths for the PDB for the following: directory objects, the Oracle XML repository for the PDB, files created with a CREATE PFILE statement, and the export directory for Oracle wallets?

The PATH_PREFIX clause does not affect files created by Oracle Managed Files.

Include a PATH_PREFIX clause that specifies an absolute path.

Set the PATH_PREFIX clause to NONE or omit it.

Creating a PDB from the PDB seed or an application seed

Cloning a PDB

Relocating a PDB

Plugging in an unplugged PDB

Is the PDB a reference PDB with a dependent proxy PDB, and is the port number of its listener changing to a value other than 1521?

Include a PORT clause and specify the port number of the listener for the PDB being created.

For example, you might have a listener network for the physical host name and default port and configure a second listener bound to a virtual host name and virtual IP address with a nondefault port number.

Omit the PORT clause.

Creating a PDB from the PDB seed or an application seed

Cloning a PDB

Relocating a PDB

Plugging in an unplugged PDB

Do you want to be able to refresh the PDB to propagate changes from the source PDB to the clone PDB?

A refreshable PDB must be opened in read-only mode.

Include a REFRESH MODE MANUAL or REFRESH MODE EVERY minutes clause.

Omit the REFRESH MODE clause or include a REFRESH MODE NONE clause.

Cloning a PDB

Do you want to grant predefined Oracle roles to the PDB_DBA role locally in the PDB?

The new administrator for the PDB is granted the PDB_DBA common role locally in the PDB. By default, the CREATE PLUGGABLE DATABASE statement does not grant the administrator or the role any privileges.

Include the ROLES clause and specify the predefined Oracle roles to grant to the PDB_DBA role. The specified roles are granted to the PDB_DBA role locally in the PDB. The user who runs the CREATE PLUGGABLE DATABASE statement does not need to be granted the specified roles. See Oracle Database Security Guide for information about predefined Oracle roles.

Omit the ROLES clause.

Creating a PDB from the PDB seed or an application seed

Creating a proxy PDB

Do you want to use a SERVICE_NAME_CONVERT clause to rename the user-defined services of the new PDB based on the service names of the source PDB?

Include a SERVICE_NAME_CONVERT clause that specifies the new name of a service and the service name it is replacing. Specify multiple service names and replacement service names if necessary.

Omit the SERVICE_NAME_CONVERT clause.

Creating a PDB from the application seed, but not a PDB seed

Cloning a PDB

Relocating a PDB

Creating a proxy PDB (Only applies to data files in the SYSTEM and SYSAUX tablespaces.)

Plugging in an unplugged PDB

Do you want to clone a PDB using a storage-managed snapshot (not a snapshot generated by ALTER PLUGGABLE DATABASE SNAPSHOT)?

Specify a SNAPSHOT COPY clause to clone a PDB using storage-managed snapshots. SNAPSHOT COPY is supported only if the underlying file system supports storage snapshots.

A snapshot copy is nearly instantaneous because it does not require copying the full data files of the source PDB. However, you cannot unplug a snapshot copy PDB from the CDB root or application root. Also, if a snapshot copy PDB exists, then you cannot drop the storage snapshot on which the snapshot copy PDB is based.

The process of materializing transforms a snapshot copy PDB, which uses sparse files, into a full PDB. Materialize a PDB by running the ALTER PLUGGABLE DATABASE MATERIALIZE command.

Omit the SNAPSHOT COPY clause.

Cloning a PDB

Do you want to enable PDB-level snapshots using ALTER PLUGGABLE DATABASE SNAPSHOT?

Specify a SNAPSHOT MODE clause in the ALTER PLUGGABLE DATABASE SNAPSHOT command, and specify MANUAL or EVERY snapshot_interval [MINUTES|HOURS].

Omit the SNAPSHOT MODE clause or specify SNAPSHOT MODE NONE.

Creating a PDB from the PDB seed or an application seed

Cloning a PDB

Relocating a PDB

Creating a proxy PDB (Only applies to data files in the SYSTEM and SYSAUX tablespaces.)

Plugging in an unplugged PDB

Are all source files in a single directory with new file names that would require multiple SOURCE_FILE_NAME_CONVERT entries?

Specify the SOURCE_FILE_DIRECTORY with the full absolute path to the source files.

Omit the SOURCE_FILE_DIRECTORY clause.

Plugging in an unplugged PDB using an XML file directly.

This clause does not apply to plugging in an unplugged PDB with a .pdb archive file.

Do the contents of the XML file accurately describe the locations of the source files?

Omit the SOURCE_FILE_NAME_CONVERT clause.

Use the SOURCE_FILE_NAME_CONVERT clause to specify the source file locations.

Plugging in an unplugged PDB using an XML file directly.

This clause does not apply to plugging in an unplugged PDB with a .pdb archive file.

Do you want to include the new PDB in one or more standby CDBs?

Specify ALL, ALL EXCEPT, or a list of standby CDBs.

When creating a remote clone, you can set the initialization parameter STANDBY_PDB_SOURCE_FILE_DBLINK to the name of the database link that points to the source PDB data files. The operation copies the data files only if the source PDB is open read-only.

Omit the STANDBYS clause or specify NONE.

Creating a PDB from the PDB seed or an application seed

Cloning a PDB

Relocating a PDB

Plugging in an unplugged PDB

Do you want to limit the amount of storage that the PDB can use?

Specify a STORAGE clause with the appropriate limits.

Omit the STORAGE clause, or specify unlimited storage using the STORAGE clause.

Creating a PDB from the PDB seed or an application seed

Cloning a PDB

Relocating a PDB

Plugging in an unplugged PDB

Do you want to reuse the temp file if a temp file exists in the target location?

Include the TEMPFILE REUSE clause.

Omit the TEMPFILE REUSE clause.

Ensure that there is no file with the same name as the new temp file in the target location.

Creating a PDB from the PDB seed or an application seed

Cloning a PDB

Relocating a PDB

Plugging in an unplugged PDB

Do you want to specify which tablespaces are included in the new PDB and which tablespaces are excluded from the new PDB?

Include the USER_TABLESPACES clause and specify the tablespaces that are included in the new PDB.

Omit the USER_TABLESPACES clause.

Plugging in an unplugged PDB

Do you want to plug an unplugged PDB into a CDB?

Include the USING filename clause.

If you are plugging in a PDB to a primary CDB in a Data Guard scenario, then set the STANDBY_PDB_SOURCE_FILE_DIRECTORY initialization parameter to a standby location that contains the source data files for instantiating the PDB. If not found, then the standby database tries to locate the files in the OMF location. If not found in the OMF location, then copy the data files to the OMF location, and restart redo apply on the standby database.

Omit the USING filename clause.

Plugging in an unplugged PDB

Do you want to create a new PDB based on a PDB snapshot?

Include the USING SNAPSHOT clause and specify either the PDB snapshot name, SCN, or timestamp. The result is a full, standalone PDB.

A PDB snapshot is a point-in-time copy of a PDB. The source PDB can be open read-only or read/write while the snapshot is created. To create PDB-level snapshots manually, specify the SNAPSHOT clause of CREATE PLUGGABLE DATABASE (or ALTER PLUGGABLE DATABASE). Specifying the EVERY interval clause configures the PDB to create snapshots automatically.

Note: PDB-level snapshots are different from storage-managed snapshots.

Exclude the USING SNAPSHOT clause.

Cloning a PDB snapshot

Do you want to clone a PDB that resides in Oracle ASM by splitting a mirror?

Include the USING MIRROR COPY clause and specify the name of the mirror copy and the source PDB.

Omit the USING MIRROR COPY clause.

Cloning a PDB that uses Oracle ASM storage