An Oracle Database installation that contains at least one PDB. A PDB appears to an Oracle Net client as a traditional Oracle database. Every Oracle database is either a CDB or a non-CDB.

A database administrator who manages a CDB. A PDB administrator manages individual PDBs within the CDB.

In a multitenant container database (CDB), a collection of schemas, schema objects, and nonschema objects to which all PDBs belong. Every CDB has exactly one root container, which stores the system metadata required to manage PDBs. All PDBs belong to the CDB root.

In a multitenant container database (CDB), a database user that exists with the same identity in multiple containers. A common user created in the CDB root has the same identity in every existing and future PDB. A common user created in an application container has the same identity in every existing and future application PDB in this application container.

In a multitenant container database (CDB), either the root or a PDB.

In a CDB, a table or view containing data pertaining to multiple containers and possibly the CDB as a whole, along with mechanisms to restrict data visible to specific common users through such objects to one or more containers. Examples of container data objects are Oracle-supplied views whose names begin with V$ and CDB_.

In a CDB, a DDL statement that affects the CDB itself, multiple containers, multiple common users or roles, or a container other than the one to which the user is connected. Only a common user connected to the root can perform cross-container operations.

In a PDB, an internal mechanism that points to data (not metadata) in the root. For example, AWR data resides in the root. Each PDB uses an object link to point to the AWR data in the root, thereby making views such as DBA_HIST_ACTIVE_SESS_HISTORY and DBA_HIST_BASELINE accessible in each separate container.

The general process of moving data from one or more non-CDBs into a multitenant container database (CDB).

A common object that exists either in the CDB root or an application root. The data, rather than the metadata, is shared by any PDB that contains a data link that points to the common object.

A hybrid of a data-linked common object and a metadata-linked common object. For an extended data-linked object, each application PDB can create its own PDB-specific data while sharing the common data in the application root.

Cloning a PDB while the source PDB is open in read/write mode.

The use of a separate set of undo data files for each PDB in a CDB.

In a multitenant container database (CDB), any user that is not a common user.

In a PDB, an internal mechanism that points to a dictionary object definition stored in the root. For example, the OBJ$ table in each PDB uses a metadata link to point to the definition of OBJ$ stored in the root.

A common object that exists either in the CDB root or an application root. The metadata, rather than the data, is shared by any PDB that contains a metadata link that points to the common object.

The architecture that enables an Oracle database to function as a multitenant container database (CDB), which means that it can contain multiple PDBs. A PDB is a portable collection of schemas, schema objects, and nonschema objects that appears to an Oracle Net client as a traditional Oracle database (non-CDB).

See CDB.

An Oracle database that is not a multitenant container database (CDB). Before Oracle Database 12c, all databases were non-CDBs. Starting in Oracle Database 12c, every database must be either a CDB or a non-CDB.

A database option that enables you to create multiple PDBs in a CDB.

In a multitenant container database (CDB), a portable collection of schemas, schema objects, and nonschema objects that appears to an Oracle Net client as a traditional Oracle database (non-CDB).

A database administrator who manages one or more PDBs. A CDB administrator manages the whole CDB.

A compressed file that contains both PDB data files and an XML metadata file. You can create a PDB by specifying the archive file, and thereby avoid copying the XML file and the data files separately.

A security mechanism to restrict operations that are available to local users connected to a specified PDB. A typical use is to limit the effect of a grant privilege. For example, you limit the grant of ALTER SYSTEM to only those options whose names begin with PLSQL.

Within a CDB, a restore point that usable only for a specific PDB. In contrast, a CDB restore point is usable by all PDBs.

The user-initiated update of the application in an application PDB to the latest version and patch in the application root.

In the multitenant architecture, the guarantee that a PDB behaves the same as a non-CDB as seen from a client connecting with Oracle Net.

See PDB.

A PDB that references a PDB in a remote CDB using a database link. The remote PDB is called a referenced PDB.

The PDB that is referenced by a proxy PDB. A local PDB is in the same CDB as its referenced PDB, whereas a remote PDB is in a different CDB.

A read-only clone that can periodically synchronize with its source PDB. Depending on the value in the REFRESH MODE clause, the synchronization occurs either automatically or manually.

A container for resource plan directives that specify how resources are allocated to resource consumer groups.

A set of limits and controls for CPU, physical I/O, or logical I/O consumption for sessions in a consumer group.

In a multitenant container database (CDB), a default pluggable database (PDB) that the system uses as a template for user-created PDBs. A PDB seed is either the system-supplied PDB$SEED or an application seed.