UTLU102S.SQL, UTLU111S.SQL, UTLU112S.SQL and UTLU121S.SQL May Show Different Results Than Select From DBA_REGISTRY (Doc ID 456845.1)

Last updated on JULY 24, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 12.2.0.1 [Release 10.2 to 12.2]
Oracle Database - Standard Edition - Version 10.2.0.1 to 12.2.0.1 [Release 10.2 to 12.2]
Information in this document applies to any platform.

Symptoms

When upgrading an Oracle database, the Oracle Database Upgrade Guide suggests that when the upgrade is completed, run one of these scripts to display the results of the upgrade:

 @utlu102s.sql
 @utlu111s.sql
 @utlu112s.sql
@utlu121s.sql
@utlu122s.sql
@utlusts.sql
When using  the Database Upgrade Assistant, DBUA, utlusts.sql is executed at the end of catupgrd.sql, and the
results are printed in files upg_summary.log, catupgrd0.log.


The typical results from running one of these scripts (in this example, utlu102s.sql) is:

Oracle Database 10.2 Upgrade Status Utility 04-20-2005 05:18:40

.
Component Status Version HH:MM:SS
Oracle Database Server VALID 10.2.0.1.0 00:11:37
JServer JAVA Virtual Machine VALID 10.2.0.1.0 00:02:47
Oracle XDK VALID 10.2.0.1.0 00:02:15
Oracle Database Java Packages VALID 10.2.0.1.0 00:00:48
Oracle Text VALID 10.2.0.1.0 00:00:28
Oracle XML Database VALID 10.2.0.1.0 00:01:27
Oracle Workspace Manager VALID 10.2.0.1.0 00:00:35
Oracle Data Mining VALID 10.2.0.1.0 00:15:56
Messaging Gateway VALID 10.2.0.1.0 00:00:11
OLAP Analytic Workspace VALID 10.2.0.1.0 00:00:28
OLAP Catalog VALID 10.2.0.1.0 00:00:59
Oracle OLAP API VALID 10.2.0.1.0 00:00:53
Oracle interMedia VALID 10.2.0.1.0 00:08:03
Spatial VALID 10.2.0.1.0 00:05:37
Oracle Ultra Search VALID 10.2.0.1.0 00:00:46
Oracle Label Security VALID 10.2.0.1.0 00:00:14
Oracle Expression Filter VALID 10.2.0.1.0 00:00:16
Oracle Enterprise Manager VALID 10.2.0.1.0 00:00:58
.
Total Upgrade Time: 00:56:09


Similar results occur for utlu111s.sql, utlu112s.sql, utlu121s.sql, utlu122s.sql and utlusts.sql

However there is a possibility that, during the upgrade, one of these components may not have been updated correctly and therefore may show a different status other than VALID, such as INVALID, NO SCRIPT, or UPGRADED.

There are numerous reasons why a component may end up in a state other than VALID, those issues will not be discussed in this document. However if, after an upgrade, you had components with a status other than VALID and either you or Oracle support has corrected the issue, running the script again will still show that same status as preciously.

If you query DBA_REGISTRY

select comp_id, version, status from DBA_registry;


you notice that the status has changed and now reflects what you would expect the correct value to be (VALID)

The example above is for 10.2.0, but this same issue also affects 11.1.X,11.2.X 12.1.X, and 12.2.X Oracle RDBMS releases

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms