Oracle Database / Multitenant, Patching & Deployment
Check allocation rights inside the application's PDB
A schema can have a quota in one PDB and none in another. Connect through the intended service before diagnosing allocation failures.
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 SYS_CONTEXT('USERENV','CON_NAME') AS con_name FROM dual;
SELECT username, tablespace_name, bytes, max_bytes FROM dba_ts_quotas WHERE username = 'APP_OWNER';Read the result
The container result anchors the quota evidence. Identical usernames in another PDB do not imply shared local storage rights.
Resolve and verify
Compare the intended owner and tablespace with the failing object, then have the DBA assign the approved bounded quota in the correct PDB.
Operational precautions
Do not change root quotas or grant unlimited storage across containers to repair one local schema.