Upgrading to Oracle 12c - Expert Consolidation in Oracle Database 12c - page 431

■ Note if you want you can still run the upgrade serially, by passing the -n 0 option to catctl.pl.

After the completion of the perl script you will notice that the database has already been shut down. The next
mandatory step is to start it normally and run the post-upgrade script, utlu121s.sql after the database has been started
normally. In the database which has just migrated, the following output was produced by the script:

SQL> @?/rdbms/admin/utlu121s
.
Oracle Database 12.1 Post-Upgrade Status Tool 08-13-2013 00:59:59
.
Component Current Version Elapsed Time
Name Status Number HH:MM:SS
.
Oracle Server
. UPGRADED 12.1.0.1.0 00:08:13
JServer JAVA Virtual Machine
. VALID 12.1.0.1.0 00:02:02
Oracle Workspace Manager
. VALID 12.1.0.1.0 00:00:58
Oracle XDK
. VALID 12.1.0.1.0 00:00:27
Oracle XML Database
. VALID 12.1.0.1.0 00:03:02
Oracle Database Java Packages
. VALID 12.1.0.1.0 00:00:10
Final Actions
. 00:01:17
Total Upgrade Time: 00:16:23

PL/SQL procedure successfully completed.

Before handing the database over for testing you need to ensure that the catuppst.sql script in
$ORACLE_HOME/rdbms/admin has been executed as part of the upgrade which it normally has unless the upgrade
process has run into an error condition.
After that script has completed it is recommended to follow it up with the execution of the utlrp.sql script to
recompile objects that have become invalid in the process. At the end of its execution you should not have additional
objects in the dba_objects view with a status of “INVALID”. Oracle provides a script to check for new invalid objects as
a result of the migration named utluiobj.sql .

SQL> @?/rdbms/admin/utluiobj
.
Oracle Database 12.1 Post-Upgrade Invalid Objects Tool 08-13-2013 01:02:45
.
This tool lists post-upgrade invalid objects that were not invalid
prior to upgrade (it ignores pre-existing pre-upgrade invalid objects).
.
Owner Object Name Object Type
.

PL/SQL procedure successfully completed.