Oracle Database / Multitenant, Patching & Deployment
Investigate a PDB that remains closed after an instance restart
A PDB's desired restart behavior must be managed explicitly in the environment. Check saved state rather than assuming it follows the root.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT con_id, con_name, instance_name, state, restricted FROM dba_pdb_saved_states;Read the result
Saved-state entries show recorded open behavior for the relevant instance. RAC and service-managed startup procedures require instance-specific interpretation.
Resolve and verify
Compare saved state with the approved restart plan and cluster management. Have the DBA record the intended state after verifying the PDB is ready.
Operational precautions
Do not save an accidental maintenance or restricted state as the future production default.