Oracle Database / Multitenant, Patching & Deployment
ORA-65114: check the PDB storage limit separately from disk space
A PDB can hit its assigned storage ceiling while its files or ASM disk group still have capacity. Inspect the PDB's defined limit.
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 name, total_size, max_size FROM v$pdbs WHERE name = 'APPPDB';
Read the result
In V$PDBS, compare current file allocation and maximum size in the correct container context. Check the installed release and interpret any unlimited setting through its documentation.
Resolve and verify
Check the complete error and PDB storage properties, then have the DBA adjust the approved limit or control growth after checking underlying storage.
Operational precautions
Do not assume adding a datafile bypasses a PDB-level ceiling. Validate the release-specific metadata before using this example.