PDB & Multitenant

How to save a PDB open state in Oracle Multitenant

Preserve a PDB open state so it returns to that mode after a CDB restart, with ALTER PLUGGABLE DATABASE SAVE STATE.

Create a new PDB as a local clone of an existing one with CREATE PLUGGABLE DATABASE ... FROM, then open it.

Plug a previously unplugged PDB into a CDB using its XML manifest, with CREATE PLUGGABLE DATABASE ... USING, then check for violations.

Open a pluggable database READ WRITE or close it with ALTER PLUGGABLE DATABASE, then verify the open mode.

Check which PDBs have a saved open state, so they reopen automatically when the CDB restarts, from DBA_PDB_SAVED_STATES.

Find which container your session is in and list all containers in the CDB, from SYS_CONTEXT and V$CONTAINERS.

List the pluggable databases in a CDB with their open mode, restricted flag, and size, from V$PDBS and CDB_PDBS.

Permanently drop a pluggable database with DROP PLUGGABLE DATABASE, with the INCLUDING versus KEEP DATAFILES options.

Find plug-in violations (option, patch, or parameter mismatches) that keep a plugged PDB from opening cleanly, from PDB_PLUG_IN_VIOLATIONS.

Unplug a PDB into an XML manifest so it can be plugged into another CDB, using ALTER PLUGGABLE DATABASE UNPLUG INTO.

Create a new pluggable database from PDB$SEED with a local admin user, using CREATE PLUGGABLE DATABASE, then open it.

PL/SQL report that walks every PDB in a container database and prints per-tablespace growth history plus 30/60/90 day projections from AWR.