Oracle Database / Multitenant, Patching & Deployment
Check PDB open state when a service stops accepting logins
The CDB instance can be running while an application's PDB is mounted or restricted. Inspect the correct container from an authorized root session.
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, name, open_mode, restricted FROM v$pdbs ORDER BY con_id;Read the result
OPEN_MODE and RESTRICTED identify each visible PDB's current state. Root availability does not establish application PDB readiness.
Resolve and verify
Compare the intended PDB with its service registration and maintenance history. Restore the approved open state through the DBA's normal management process.
Operational precautions
Do not open every PDB or remove restricted mode while maintenance is still in progress.