There are changes in this document for recent releases of Oracle Database.
Changes in Oracle Database Release 19c, Version 19.1
Oracle Multitenant Administrator's Guide for Oracle Database release 19c, version 19.1 has the following changes.
The following major features are new in this release.
Enhancements to database-managed PDB snapshots
When the initialization parameter
TRUE, database-managed snapshots create sparse copies of the data files of the source PDB. Starting in Oracle Database 19c, you can create database-managed snapshot clone PDBs from a source PDB that is open read/write. In previous releases, the source PDB needed to remain read-only and unchanging for the lifetime of any snapshot clone PDB.
Because the source PDB is not required to be in read-only mode, you can create snapshots of a production database, and then clone PDBs from these snapshots. Also, the snapshots in a snapshot carousel can be sparse copies, enabling the carousel to consume dramatically less storage than in previous releases.
See "Contents of a PDB Snapshot".
Workload capture and replay in a PDB
A local user can capture, replay, and report on a workload at the PDB level.
ADDM analysis for PDBs
You can use ADDM to analyze AWR data stored inside the PDB through an AWR snapshot taken inside the PDB. You can also analyze AWR data of a non-CDB, CDB root, or PDB imported into the AWR storage of a PDB. Automatic ADDM of a PDB is disabled by default. You can enable it for a PDB by enabling automatic AWR snapshots.
Database Vault Operations Control for infrastructure database administrators
You can use Oracle Database Vault to block common users (for example, infrastructure DBAs) from accessing local data in PDBs. Thus, common users are blocked from accessing local data. It enables you to store sensitive data for your business applications and allow operations to manage the database infrastructure without having to access sensitive customer data.
Support for multiple PDB shards in the same CDB
A single CDB can contain multiple PDBs as shard catalog databases. Also, a CDB can contain shard PDBs from different sharded databases (SDBs), each managed by its own separate catalog database.
Automated PDB relocation
In Oracle Grid Infrastructure, you can use Fleet Patching and Provisioning to automate relocation of a PDB from one CDB to another. Automated relocation enables individual PDBs to be patched more quickly without exposing other PDBs to the changes in the patch.
Cloning a remote PDB using DBCA
You can clone a remote PDB using DBCA in silent mode.
See "About Cloning a Remote PDB".
Remote PDB relocation
You can use Database Configuration Assistant (DBCA) to relocate a PDB from a remote CDB to a local CDB.
Cloud object store support for Data Pump Import
impdbspecifies the name of a credential object that contains the user name and password required to access an object store bucket. You can also specify a default credential using the database property
Oracle Database Licensing Information User Manual for details on which features are supported for different editions and services
Changes in Oracle Database Release 18c, Version 18.1
The following are changes in Oracle Multitenant Administrator's Guide for Oracle Database release 18c, version 18.1.
The following features are new in this release:
A CDB fleet is a collection of different CDBs that can be managed as one logical CDB.
See "Administering a CDB Fleet".
PDB snapshot carousel
A PDB snapshot is a point-in-time copy of a PDB. You can create snapshots manually using the
CREATE PLUGGABLE DATABASE(or
ALTER PLUGGABLE DATABASE), or automatically using the
EVERY intervalclause. When a PDB is enabled for snapshots, you can create multiple snapshots (point-in-time copies) of the PDB. The library of snapshots is called a PDB snapshot carousel. You can quickly clone a new PDB based on any snapshot in the carousel. In this way, you can perform point-in-time recovery to any snapshot in the carousel, or rapidly create a PDB by cloning any snapshot.
A container map enables a session to issue SQL statements that are routed to the appropriate PDB, depending on the value of a predicate used in the SQL statement. The partitioning column in the map table does not need to match a column in the metadata-linked table. For example, if the table
salesis enabled for the container map
pdb_map_tbl, and if
salesdoes not have the column used to partition
pdb_map_tbl, then queries with the predicate
CONTAINERS(sales)are still routed to the PDBs specified in the map table.
See "Container Maps".
Refreshable PDB switchover
A refreshable clone PDB is a read-only clone that can periodically synchronize with its source PDB. You can reverse the roles, transforming the source PDB into the clone and the clone into the source. This technique can be useful for load balancing. Also, if the source PDB fails, then you can resume operations on the clone PDB, rendering a CDB-level Oracle Data Guard failover unnecessary.
Lockdown profile enhancements
You can create, alter, or drop lockdown profiles in application containers. Also, you can create lockdown profiles based on a static or a dynamic base profile.
You can use DBCA to clone a local PDB or duplicate a CDB. Duplication is only supported in silent mode.
Usable backups of non-CDBs and relocated PDBs
When you are cloning a non-CDB as a PDB or relocating a PDB, you can use the
DBMS_PDB.EXPORTRMANBACKUPprocedure to export RMAN backup metadata into the PDB dictionary. This metadata enables backups of the source non-CDB or PDB to be usable for restore and recovery of the target PDB.
RMAN duplication of a PDB to another CDB
You can clone a PDB from a source CDB to an existing CDB that is open read/write.
Relocation of sessions during planned maintenance
Application Continuity can drain database sessions during planned maintenance when the application submits a connection test, at request boundaries, and at good places to fail over. The relocation is transparent to applications. This feature is on by default for all maintenance operations invoked at the database service and PDB levels: stop service, relocate service, relocate PDB, and stop PDB.
Copying a PDB in an Oracle Data Guard environment
When performing a remote clone in a primary database, or plugging in a PDB in a primary database, you can set initialization parameters in a standby database that automates copying the data files for the newly created PDB.
Parallel statement queuing at the PDB level
You can configure parallel statement queuing for a PDB just as for a non-PDB using the
PARALLEL_SERVERS_TARGETinitialization parameter. At the PDB level, the default is based on the
CPU_COUNTsetting for the PDB. At the CDB level, the default value is the value of the
See "Utilization Limits for PDBs".
Split mirror clone PDBs
When a PDB resides in Oracle ASM, you can use a split mirroring technique to clone a PDB. The cloned PDB is independent of the original PDB. The principal use case is to rapidly provision test and development PDBs in an Oracle ASM environment.