Oracle Database 19c: Multitenant Architecture

Compare the deprecated single-tenant architecture with the multi-tenant container database (CDB) and its pluggable databases (PDBs), including the CDB root and seed, with benefits like centralized management and reduced overhead.

Set up a VirtualBox virtual machine, install Oracle Linux 8.8, allocate 4 GB memory, 2 CPUs, 60 GB disk, create /u01 partitions, and install Oracle 19c for multitenant architecture practice.

Create a container database (CDB) in Oracle 19c using DBCA in graphical or silent mode. Oracle recommends DBCA for automation, then clone, plug in and unplug PDBs, or duplicate CDBs.

Use the DBCA GUI to create a multitenant CDB in Oracle 19c, configure storage with file system and omf, set memory and listener, and save a response file.

Learn to create a CDB with DBCA in silent mode using a response file, but the syntax is complex and not recommended; the graphical interface is easier.

Set the Oracle SID to prod, connect with SQL Plus, verify the listener status, and compare SPFILE versus PFILE initialization parameters while inspecting CDB root and PDBs.

Explore Oracle database instances and memory structures, including SGA and PGA, memory management options, and core components such as shared pool, library cache, and buffer cache.

Create a pluggable database (PDB) with DBCA graphical interface or SQL Plus, using a CDB, admin user, and Oracle managed files (OMF); verify data files and open in read-write mode.

Create a pluggable database with the create command from the PDB seed using Oracle managed files, then open it in read-write mode and switch containers with alter session set container.

Close a pluggable database with alter pluggable database close, then open it in read-only or read-write mode. Do not use shutdown from the CDB root; set startup state instead.

Create the first local tablespace and user in PDB one by configuring a 100 MB auto extend data file, then grant necessary privileges and verify connectivity.

Create and manage pluggable database services, assign pdb admin users, and connect to pdbs using service names and the dbms_service package in a multitenant Oracle 19c environment.

Shut down and start up an Oracle multitenant database by using alter pluggable database to close and open PDBs in read write or read only, with shutdown and startup options.

Describe how to set default permanent and temporary tablespaces in a pluggable database, using database properties and PDB3 commands to verify and switch containers.

Learn how common versus local users and roles operate in Oracle multitenant architecture, using CDB roots and PDBs to manage access with container all and container clause.

Learn to manage pluggable databases in Oracle 19c, including renaming a PDB global name, switching containers, opening in restricted mode, and unplugging or dropping the PDB.

Alter system or alter session to change initialization parameters in Oracle multitenant databases, across CDB and PDB, using memory, spfile, and pfile scopes, with PDB inheritance.

Explore Oracle multitenant administration views and data dictionary views, from CDB and DBA views to all and user views, and learn how dynamic v$ views monitor sessions and database activity.

Learn to back up and recover in Oracle multitenant architecture using RMAN, performing CDB and PDB level backups, and handling archive logs, control files, and password files.

Explore application containers inside a container database, where each container holds a versioned set of common data and metadata for one or more backends, such as marketing or finance PDBs.

Create an application container with its application root in install mode to establish shared metadata and data, define pdbs, and partition data by department or region.

Install the application by creating shared data and metadata in the application container, entering installation mode, then configure the application name and version and create a tablespace, user, and table.

Create and synchronize application PDBs from a seed in Oracle 19c multitenant architecture. Open the seed, then create PDBs and switch across root and application containers.

Activate upgrade mode for application PDBs, synchronize each PDB with the root, and create new objects before ending the upgrade to reach version 1.1.

Learn to use container mapping by creating a container map table to partition data across multiple application PDBs, enable container mapping, and query via the application route without containers class.

Learn to create common and local users and roles in an Oracle application container, distinguishing application root from CDB root and app PDBs, with upgrades and grants across containers.