After upgrade CATPROC and CATALOG comps are INVALID even if only user invalid objects are found
(Doc ID 745183.1)
Last updated on NOVEMBER 14, 2019
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 9.2 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
After upgrade from 22.214.171.124 to 10.2.0.4 there are invalid components under dba_registry:
Oracle Database 10.2 Upgrade Status Utility 09-17-2008 18:01:00
Component Status Version
Oracle Database Server INVALID 10.2.0.4.0
JServer JAVA Virtual Machine VALID 10.2.0.4.0
Oracle XDK VALID 10.2.0.4.0
Oracle Database Java Packages INVALID 10.2.0.4.0
Oracle XML Database VALID 10.2.0.4.0
Oracle Workspace Manager VALID 10.2.0.4.3
No critical errors have been found in the spool file for the run of the upgrade script.
No SYS/SYSTEM invalid objects have been found.
The select which indicates the invalid objects that caused the invalidation of the CATALOG or CATPROC return only user invalid objects.
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