Oracle Database / Multitenant, Patching & Deployment
Inspect Oracle component registry after an upgrade
A database can open while an installed component remains invalid or incompletely upgraded. Check registry state before declaring the maintenance complete.
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 comp_id, comp_name, version, status FROM dba_registry ORDER BY comp_id;Read the result
The registry shows installed component versions and status in the queried container. Compare expected components across relevant PDBs as well as root.
Resolve and verify
Review upgrade logs for the affected component and follow the documented remediation. Validate dependent applications after the component is healthy.
Operational precautions
Do not run arbitrary catalog scripts or remove a component to make the registry appear clean.