Starting up a CDB instance

To start a CDB instance, the current user must be a common   user whose current container is the root.

When you open a CDB, its PDBs are mounted. Use the  ALTER   PLUGGABLE   DATABASE statement   to modify the open mode of one or more PDBs.

Managing processes

A CDB has one set of background processes shared by the root   and all PDBs.

Managing memory

A CDB has a single system global area (SGA) and a single   aggregate program glob

al area (PGA). The memory required by a CDB is the sum   of the memory requirements for all of the PDBs that will be part of the CDB.

Managing security

You can create and drop common users and local users in a CDB.   You can also grant privileges to and revoke privileges from these users. You   can also manage the  CONTAINER_DATA  attributes   of common users.

In addition, grant the following roles to the appropriate   users:

·           Grant the  CDB_DBA  role   to CDB administrators.

·           Grant the  PDB_DBA  role   to PDB administrators.

Monitoring errors and alerts

A CDB has one alert log for the entire CDB. The name of a PDB   is included in records in trace files, when appropriate.

Managing diagnostic data

In a CDB, you can use the Oracle Database fault diagnosability   infrastructure and the Automatic Diagnostic Repository (ADR).

Managing control files

A CDB has one control file.

Managing the online redo log and the archived redo log files

A CDB has one online redo log and one set of archived redo log   files.

Managing tablespaces

You can create, modify, and drop tablespaces and temporary   tablespaces for the root and for individual PDBs. You can also specify a   default tablespace, default tablespace type, and a default temporary   tablespace for the root. The root has its own set of Oracle-supplied tablespaces,   such as the  SYSTEM  tablespace,   and each PDB has its own set of Oracle-supplied tablespaces.

Managing data files and temp files

The root has its own data files, and each PDB has its own data   files. In a CDB, you can manage data files and temp files in basically the   same way you would manage them for a non-CDB. However, the following   exceptions apply to CDBs:

·           You can limit the amount of   storage used by the data files for a PDB by using the  STORAGE  clause   in a  CREATE   PLUGGABLE   DATABASE  or  ALTER   PLUGGABLE   DATABASE statement.

·           There is a default temporary   tablespace for the root and for each PDB.

Managing undo

There is one active undo tablespace for a single-instance CDB.   For an Oracle RAC CDB, there is one active undo tablespace for each instance.   In a CDB, the  UNDO_MANAGEMENT initialization   parameter must be set to  AUTO ,   and an undo tablespace is required to manage the undo data.

Only a common user who has the appropriate privileges and   whose current container is the root can create an undo tablespace. Undo   tablespaces are visible in static data dictionary views and dynamic   performance (V$) views when the current container is the root. Undo   tablespaces are visible only in dynamic performance views when the current   container is a PDB. When the current container is a PDB, an attempt to create   an undo tablespace fails without returning an error.

Moving data between PDBs

You can move data between PDBs using the same methods that you   would use to move data between non-CDBs. For example, you can transport the   data or use Data Pump export/import to move the data.

Using Oracle Managed Files

Using Oracle Managed files can simplify administration for   both a CDB and a non-CDB.

Using Transparent Data Encryption

Transparent Data Encryption is a feature that enables   encryption of individual table columns before storing them in the data file,   or enables encryption of entire tablespaces. In a CDB, each PDB has its own   master key for Transparent Data Encryption, and, where applicable, the  ADMINISTER   KEY   MANAGEMENT  SQL   statement enables key management at the CDB level and for individual PDBs.

Using a standby database

Oracle Data Guard can configure a physical standby or a   logical standby of a CDB. Data Guard operates on the entire CDB, not on   individual PDBs.

Using Oracle Database Vault

Oracle Database Vault policies are scoped to individual PDBs.

Dropping a database

When you drop a CDB, the root, seed, and all of its PDBs   (including their data) are also dropped.

You can also drop individual PDBs with the  DROP   PLUGGABLE   DATABASE  statement.

Active Session History (ASH)

ASH collects information about active database sessions. You   can use this information to analyze and identify performance issues.

Most of the ASH data is stored in memory. A small percentage   of the ASH data samples are stored in the root.

ASH data related to a PDB is not included if the PDB is   unplugged.

A common user whose current container is the root can view ASH   data for the root and for PDBs.

A user whose current container is a PDB can view ASH data for   the PDB only.

Alerts

An alert is a notification of a possible problem.

Threshold settings that pertain to a PDB are stored in the   PDB.

Alerts posted when thresholds are violated are enqueued into   the alert queue in the root.

Threshold settings that pertain to a PDB are included if the   PDB is unplugged. Alerts related to a PDB are not included if the PDB is   unplugged.

A common user whose current container is the root can view   alerts for the root and for PDBs.

A user whose current container is a PDB can view alert   thresholds and alerts for the PDB only.

Automated Database Maintenance Tasks

Automated database maintenance tasks are tasks that are   started automatically at regular intervals to perform maintenance operations   on the database. Automated tasks include automatic optimizer statistics   collection, Automatic Segment Advisor tasks, and Automatic SQL Tuning Advisor   tasks.

A user can schedule maintenance windows and enable or disable   maintenance tasks for the current container only. If the current container is   the root, then the changes only apply to the root. If the current container   is a PDB, then the changes only apply to the PDB.

Data related to a PDB is stored in the PDB for automatic   optimizer statistics collection and the Automatic Segment Advisor. This data   is included if the PDB is unplugged.

Automatic SQL Tuning Advisor runs only in the root. See the   SQL Tuning Advisor row in this table for information about data collected by   Automatic SQL Tuning Advisor.

See the appropriate row in this table for data visibility   information about the following manageability features: automatic optimizer   statistics collection, Automatic Segment Advisor, and Automatic SQL Tuning   Advisor.

Automatic Database Diagnostic Monitor (ADDM)

ADDM can diagnose a database's performance and determine how   identified problems can be resolved.

All ADDM runs must be performed in the root. All ADDM results   are stored in the root.

ADDM analyzes activity in a PDB within the context of the   current analysis target. ADDM does not analyze one PDB at a time. As in   previous releases, ADDM runs with a target of either the entire instance or   Oracle RAC database.

ADDM results related to a PDB are not included if the PDB is   unplugged.

ADDM results are visible only to a common user whose current   container is the root. The ADDM results can include information about   multiple PDBs. The ADDM results cannot be viewed when the current container   is a PDB.

Automatic Optimizer Statistics Collection

Automatic optimizer statistics collection gathers optimizer   statistics for all schema objects in the database for which there are no   statistics or only stale statistics. The statistics gathered by this task are   used by the SQL query optimizer to improve the performance of SQL execution.

When an automatic optimizer statistics collection task gathers   data for a PDB, it stores this data in the PDB. This data is included if the   PDB is unplugged.

A common user whose current container is the root can view   optimizer statistics data for PDBs.

A user whose current container is a PDB can view optimizer   statistics data for the PDB only.

Automatic Segment Advisor

The Automatic Segment Advisor identifies segments that have   space available for reclamation and makes recommendations on how to   defragment those segments.

When Automatic Segment Advisor gathers data for a PDB, it   stores this data in the PDB. This data is included if the PDB is unplugged.

A common user whose current container is the root can view   Automatic Segment Advisor data for PDBs.

A user whose current container is a PDB can view the Automatic   Segment Advisor data for the PDB only.

Automatic Workload Repository (AWR)

The AWR collects, processes, and maintains performance   statistics for problem detection and self-tuning purposes. This data is   stored in the database. The gathered data can be displayed in both reports   and views.

AWR data is stored in the root.

AWR data related to a PDB is not included if the PDB is   unplugged.

A common user whose current container is the root can view AWR   data for the root and for PDBs.

A user whose current container is a PDB can view AWR data for   the PDB only.

Database Replay

Database Replay is a feature of Oracle Real Application   Testing. Database Replay captures the workload for a database and replays it   exactly on a test database.

Information about database captures and replays are stored in   the root.

A common user whose current container is the root can view   database capture and replay information.

SQL Management Base (SMB)

SMB stores statement logs, plan histories, SQL plan baselines,   and SQL profiles in the data dictionary.

SMB data related to a PDB is stored in the PDB. The SMB data   related to a PDB is included if the PDB is unplugged.

A common user whose current container is the root can view SMB   data for PDBs.

A user whose current container is a PDB can view the SMB data   for the PDB only.

SQL Performance Analyzer (SPA)

SPA can analyze the SQL performance impact of SQL tuning and   other system changes. SPA is often used with Database Replay.

A common user whose current container is the root can run SPA   for any PDB. In this case, the SPA results data is stored in the root and is   not included if the PDB is unplugged.

A user whose current container is a PDB can run SPA on the   PDB. In this case, the SPA results data is stored in the PDB and is included   if the PDB is unplugged.

A common user whose current container is the root can view SPA   results data for PDBs.

A user whose current container is a PDB can view the SPA   results data for the PDB only.

SQL Tuning Sets (STS)

An STS is a database object that includes one or more SQL   statements along with their execution statistics and execution context, and   could include a user priority ranking.

You can use an STS to tune a group of SQL statements or test   their performance using SPA.

An STS can be stored in the root or in any PDB. If it is   stored in the root, then you can load SQL statements from any PDB into it.

When a PDB is unplugged, an STS stored in the root is not   included, even if the STS contains SQL statements from the PDB.

When a PDB is unplugged, an STS stored in the PDB is included.

A common user whose current container is the root can view STS   data stored in the root only.

A user whose current container is a PDB can view STS data for   the PDB only.

SQL Tuning Advisor

SQL Tuning Advisor optimizes SQL statements that have been   identified as high-load SQL statements.

Automatic SQL Tuning Advisor data is stored in the root. It   might have results about SQL statements executed in a PDB that were analyzed   by the advisor, but these results are not included if the PDB is unplugged.

A common user whose current container is the root can run SQL   Tuning Advisor manually for SQL statements from any PDB. When a statement is   tuned, it is tuned in any container that runs the statement.

A user whose current container is a PDB can also run SQL   Tuning Advisor manually for SQL statements from the PDB. When SQL Tuning   Advisor is run manually from a PDB, the results are stored in the PDB from   which it is run. In this case, a statement is tuned only for the current PDB,   and the results related to a PDB are included if the PDB is unplugged.

When SQL Tuning Advisor is run automatically, the results are   visible only to a common user whose current container is the root. These   results cannot be viewed when the current container is a PDB.

When SQL Tuning Advisor is run manually by a user whose   current container is a PDB, the results are only visible to a user whose   current container is that PDB.

When connected as a common user whose current container is the   root,  ALTER   DATABASE  statements   with the following clauses modify the entire CDB:

·           startup_clauses

·           recovery_clauses

·           logfile_clauses

·           controlfile_clauses

·           standby_database_clauses

·           instance_clauses

·           security_clause

·           RENAME   GLOBAL_NAME  clause

·           ENABLE   BLOCK   CHANGE   TRACKING  clause

·           DISABLE   BLOCK   CHANGE   TRACKING  clause

When connected as a common user whose current container is the   root,  ALTER   DATABASE  statements   with the following clauses modify the root only:

·           database_file_clauses

·           DEFAULT   EDITION  clause

·           DEFAULT   TABLESPACE  clause

ALTER   DATABASE  statements   with the following clauses modify the root and set default values for PDBs:

·           DEFAULT   TEMPORARY   TABLESPACE  clause

·           flashback_mode_clause

·           SET   DEFAULT  {  BIGFILE  |  SMALLFILE  }  TABLESPACE clause

·           set_time_zone_clause

You can use these clauses to set non-default values for   specific PDBs.

When connected as a common user whose current container is the   root,  ALTER   PLUGGABLE   DATABASE  statements   with the following clause can modify the open mode of one or more PDBs:

·           pdb_change_state

When the current container is a PDB,  ALTER   PLUGGABLEDATABASE  statements   with this clause can modify the open mode of the current PDB. See " Modifying a PDB with the ALTER PLUGGABLE DATABASE   Statement " .

When connected as a common user whose current container is the   root,  ALTER   PLUGGABLE   DATABASE  statements   with the following clause can preserve or discard the open mode a PDB when   the CDB restarts:

·           pdb_save_or_discard_state

CREATE   USER

Creates a local user in the current PDB.

Creates a common user.

ALTER   USER

Alters a local user in the current PDB.

Alters a common user.

CREATE   ROLE

Creates a local role in the current PDB.

Creates a common role.

GRANT

Grants a privilege in the local container to a local user,   common user, or local role.

The  SET   CONTAINER  privilege   can be granted to a user-created common user in the current PDB.

Grants a system privilege or object privilege on a common   object to a common user or common role. The specified privilege is granted to   the user or role across the entire CDB.

REVOKE

Revokes a privilege in the local container from a local user,   common user, or local role.

This statement can revoke only a privilege granted with  CURRENT  specified   in the  CONTAINER  clause   from the specified user or role in the local container. The statement does   not affect privileges granted with  ALL  specified   in the  CONTAINER  clause.

The  SET   CONTAINER  privilege   can be revoked from a user-created common user in the current PDB.

Revokes a system privilege or object privilege on a common   object from a common user or common role. The specified privilege is revoked   from the user or role across the entire CDB.

This statement can revoke only a privilege granted with  ALL  specified   in the  CONTAINER  clause   from the specified common user or common role. The statement does not affect   privileges granted with  CURRENT  specified   in the  CONTAINER  clause.   However, any privileges granted locally that depend on the privilege granted   commonly that is being revoked are also revoked.

SHUTDOWN IMMEDIATE

srvctl stop database -db db_unique_name   -stopoption immediate

SHUTDOWN TRANSACTIONAL

srvctl stop database -db db_unique_name   -stopoption transactional

SHUTDOWN ABORT

srvctl stop database -db db_unique_name -stopoption   abort

Managing tablespaces

You can create, modify, and drop tablespaces for a PDB. You   can specify a default tablespace and default tablespace type for each PDB.   Also, there is a default temporary tablespace for each PDB. You optionally   can create additional temporary tablespaces for use by individual PDBs.

Managing data files and temp files

Each PDB has its own data files. You can manage data files and   temp files in the same way that you would manage them for a non-CDB. You can   also limit the amount of storage used by the data files for a PDB by using   the  STORAGE  clause   in a  CREATE   PLUGGABLE   DATABASE  or  ALTER   PLUGGABLE   DATABASE  statement.

Managing schema objects

You can create, modify, and drop schema objects in a PDB in   the same way that you would in a non-CDB. You can also create triggers that   fire for a specific PDB.

When you manage database links in a CDB, the root has a unique   global database name, and so does each PDB. The global name of the root is   defined by the  DB_NAME  and  DB_DOMAIN initialization   parameters. The global database name of a PDB is defined by the PDB name and   the  DB_DOMAIN  initialization   parameter. The global database name of each PDB must be unique within the   domain.

MEMORY

The initialization parameter setting is changed in memory and   takes effect immediately in the PDB. The new setting affects only the PDB.

The setting reverts to the value set in the root in the any of   the following cases:

·           An  ALTER   SYSTEM   SET  statement   sets the value of the parameter in the root with  SCOPE  equal   to  BOTH  or  MEMORY ,   and the PDB is closed and re-opened. The parameter value in the PDB is not   changed if  SCOPE  is   equal to  SPFILE , and the   PDB is closed and re-opened.

·           The PDB is closed and re-opened.

·           The CDB is shut down and   re-opened.

SPFILE

The initialization parameter setting is changed for the PDB   and stored persistently. The new setting takes effect in any of the following   cases:

·           The PDB is closed and re-opened.

·           The CDB is shut down and   re-opened.

In these cases, the new setting affects only the PDB.

BOTH

The initialization parameter setting is changed in memory, and   it is changed for the PDB and stored persistently. The new setting takes   effect immediately in the PDB and persists after the PDB is closed and   re-opened or the CDB is shut down and re-opened. The new setting affects only   the PDB.