How to Diagnose Components with NON VALID Status in DBA_REGISTRY after an Upgrade
(Doc ID 753041.1)
Last updated on SEPTEMBER 20, 2018
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 220.127.116.11 [Release 10.2 to 11.2]
Information in this document applies to any platform.
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.
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.
comp_id,substr(version,1,12) version,status from dba_registry;
COMP_NAME COMP_ID VERSION STATUS
------------------------------ ---------- ------------ -----------
Oracle Enterprise Manager EM 10.2.0.3.0 VALID
Spatial SDO 18.104.22.168.0 NO_SCRIPT
Oracle interMedia ORDIM 10.2.0.3.0 VALID
OLAP Catalog AMD 10.2.0.3.0 VALID
Oracle XML Database XDB 10.2.0.3.0 INVALID
Oracle Text CONTEXT 10.2.0.3.0 VALID
Oracle Expression Filter EXF 10.2.0.3.0 VALID
Oracle Rule Manager RUL 10.2.0.3.0 VALID
Oracle Workspace Manager OWM 10.2.0.1.0 UPGRADED
Oracle Data Mining ODM 10.2.0.3.0 REMOVED
Oracle Database Catalog Views CATALOG 10.2.0.3.0 VALID
Oracle Database Packages and T CATPROC 10.2.0.3.0 VALID
JServer JAVA Virtual Machine JAVAVM 10.2.0.3.0 LOADED
Oracle XDK XML 10.2.0.3.0 VALID
Oracle Database Java Packages CATJAVA 10.2.0.3.0 VALID
OLAP Analytic Workspace APS 10.2.0.3.0 INVALID
Oracle OLAP API XOQ 10.2.0.3.0 VALID
Oracle Real Application Cluster RAC 10.2.0.3.0 OPTION OFF
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
|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:|