UTLRP shows extra line after APEX installation

Question

We have recently installed APEX 4.0 in 10.2.0.4 database and later ran utlrp.sql to compile the invalid objects.
We noticed the below line in UTLRP output :
...Database user "SYS", database schema "APEX_040000", user# "380" 14:59:11
...Compiled 0 out of 2717 objects considered, 0 failed compilation 14:59:12
...232 packages
...225 package bodies
...427 tables
...12 functions
...19 procedures
...3 sequences
...439 triggers
...1177 indexes
...175 views
...0 libraries
...4 types
...0 type bodies
...0 operators
...0 index types
...Begin key object existence check 14:59:12
...Completed key object existence check 14:59:12
...Setting DBMS Registry 14:59:12
...Setting DBMS Registry Complete 14:59:12
...Exiting validate 14:59:12
The above lines are coming from the below code which is being called from utlrp:
SQL> EXECUTE dbms_registry_sys.validate_components;
...Database user "SYS", database schema "APEX_040000", user# "380" 14:59:11
...Compiled 0 out of 2717 objects considered, 0 failed compilation 14:59:12
...232 packages
...225 package bodies
...427 tables
...12 functions
...19 procedures
...3 sequences
...439 triggers
...1177 indexes
...175 views
...0 libraries
...4 types
...0 type bodies
...0 operators
...0 index types
...Begin key object existence check 14:59:12
...Completed key object existence check 14:59:12
...Setting DBMS Registry 14:59:12
...Setting DBMS Registry Complete 14:59:12
...Exiting validate 14:59:12
PL/SQL procedure successfully completed.
==============
When i ran the same code in a database where APEX is not installed, i am not getting any messages:
SQL> EXECUTE dbms_registry_sys.validate_components;
PL/SQL procedure successfully completed.
==================
PS: I have set "serveroutput on" on both the database sessions.
Could some one please let me know why we are getting those additional lines after installaing APEX ?
Thanks in advance.

Answer 1

Hi there,
This is simply diagnostic information being emitted by the APEX component validation procedure. You would get the same output if you simply ran sys.validate_apex on the instance where APEX is installed.
This isn't anything to be alarmed about - everything looks normal to me.
Joel