Oracle Database / Multitenant, Patching & Deployment
Find invalid objects across containers with explicit CON_ID
A root-level support query can miss the PDB where an object failed. Include container identity when reviewing database-wide invalid objects.
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, owner, object_name, object_type FROM cdb_objects WHERE status = 'INVALID' ORDER BY con_id, owner FETCH FIRST 100 ROWS ONLY;Read the result
Visible rows depend on privileges and container-data access. An empty result in a restricted admin context is not proof every PDB is clean.
Resolve and verify
Map CON_ID to the intended PDB, inspect its compiler errors and repair the specific dependency. Validate application startup after the approved deployment.
Operational precautions
Do not recompile every container indiscriminately or grant broad cross-container visibility just for convenience.