My Oracle Support Banner

How to Diagnose Components with NON VALID Status in DBA_REGISTRY after an Upgrade (Doc ID 753041.1)

Last updated on JANUARY 16, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 19.5.0.0.0 [Release 10.2 to 18]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

Goal

To provide the steps and tools to diagnose components in the DBA_REGISTRY which
are showing status INVALID, LOADED, UPGRADED, NO SCRIPT, OPTION OFF, etc. after an upgrade and
provide possible solutions to resolve these status's.

Note:
If the status is shown as REMOVED then this means component is successfully removed.
In case of UPGRADE, the component was not upgraded because it was removed from the database.

For Example:

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 1. Its important to check the current status of the dba_registry and current list of invalid objects immediately after an upgrade.
 2. Was the script $ORACLE_HOME/rdbms/admin/utlrp.sql run after the upgrade?
 3. In the case of a manual upgrade, were there errors reported in the spooled output of catupgrd.sql?
 4. Was the component(s) status VALID in source database prior to the upgrade?
 5. Was the component installed and linked/enabled at the binary level for the target upgrade release?
 6. Check component dependencies:
 7. Rerun upgrade script:
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.