Oracle Database / Multitenant, Patching & Deployment
Compare SQL patch registration with the installed Oracle home
Applying binary patches and applying their SQL changes are related but distinct tasks. Inspect SQL patch history after planned maintenance.
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 patch_id, action, status, action_time, description FROM dba_registry_sqlpatch ORDER BY action_time DESC FETCH FIRST 30 ROWS ONLY;Read the result
The registry records SQL patch actions in this container. It must be compared with the intended Oracle home inventory and patch readme.
Resolve and verify
Find unsuccessful actions and inspect their patch logs. Complete the supported datapatch workflow in the required container states through the DBA.
Operational precautions
Do not rerun patch tooling blindly or assume a successful binary inventory proves all PDB SQL changes succeeded.