INVALID Components found during APEX upgrade
Hi, I am trying to upgrade APEX 3.x to 4.2.1 and the prereq script found invalid XML Database - do I need to deinstall, reinstall XDB?
I found that all these are INVALID - what is the diagnois? :)
col COMP_NAME FORMAT A30
col VERSION FORMAT A13
col STATUS FORMAT A10
col STATUS FORMAT A10
select COMP_NAME, VERSION, STATUS, MODIFIED
from sys.dba_registry
where status = 'INVALID'
COMP_NAME VERSION STATUS MODIFIED
--------------------------
Oracle Workspace Manager 10.2.0.5.0 INVALID 24-AUG-2011 13:41:39
Oracle interMedia 10.2.0.5.0 INVALID 24-AUG-2011 13:41:42
Spatial 10.2.0.5.0 INVALID 24-AUG-2011 13:41:42
Oracle Text 10.2.0.5.0 INVALID 24-AUG-2011 13:41:42
Oracle XML Database 10.2.0.5.0 INVALID 24-AUG-2011 13:41:44
Oracle Data Mining 10.2.0.5.0 INVALID 24-AUG-2011 13:41:44
Oracle Application Express 3.2.0.00.27 INVALID 24-AUG-2011 13:41:48
Thanks, Bill
I found that all these are INVALID - what is the diagnois? :)
col COMP_NAME FORMAT A30
col VERSION FORMAT A13
col STATUS FORMAT A10
col STATUS FORMAT A10
select COMP_NAME, VERSION, STATUS, MODIFIED
from sys.dba_registry
where status = 'INVALID'
COMP_NAME VERSION STATUS MODIFIED
--------------------------
Oracle Workspace Manager 10.2.0.5.0 INVALID 24-AUG-2011 13:41:39
Oracle interMedia 10.2.0.5.0 INVALID 24-AUG-2011 13:41:42
Spatial 10.2.0.5.0 INVALID 24-AUG-2011 13:41:42
Oracle Text 10.2.0.5.0 INVALID 24-AUG-2011 13:41:42
Oracle XML Database 10.2.0.5.0 INVALID 24-AUG-2011 13:41:44
Oracle Data Mining 10.2.0.5.0 INVALID 24-AUG-2011 13:41:44
Oracle Application Express 3.2.0.00.27 INVALID 24-AUG-2011 13:41:48
Thanks, Bill
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you! I am going to look now..
ASKER
OK, Looked at first one:
SQL> set serveroutput on
SQL> exec validate_apex
PL/SQL procedure successfully completed.
COMP_NAME VERSION STATUS MODIFIED
--------------------------
Oracle Workspace Manager 10.2.0.5.0 INVALID 24-AUG-2011 13:41:39
Oracle interMedia 10.2.0.5.0 INVALID 24-AUG-2011 13:41:42
Spatial 10.2.0.5.0 INVALID 24-AUG-2011 13:41:42
Oracle Text 10.2.0.5.0 INVALID 24-AUG-2011 13:41:42
Oracle XML Database 10.2.0.5.0 INVALID 24-AUG-2011 13:41:44
Oracle Data Mining 10.2.0.5.0 INVALID 24-AUG-2011 13:41:44
6 rows selected.
Looks like it VALIDed
Oracle Application Express 3.2.0.00.27 VALID 01-JUN-2013 10:23:35
BUT, XDB is still INVALID
Looking at second link....
SQL> set serveroutput on
SQL> exec validate_apex
PL/SQL procedure successfully completed.
COMP_NAME VERSION STATUS MODIFIED
--------------------------
Oracle Workspace Manager 10.2.0.5.0 INVALID 24-AUG-2011 13:41:39
Oracle interMedia 10.2.0.5.0 INVALID 24-AUG-2011 13:41:42
Spatial 10.2.0.5.0 INVALID 24-AUG-2011 13:41:42
Oracle Text 10.2.0.5.0 INVALID 24-AUG-2011 13:41:42
Oracle XML Database 10.2.0.5.0 INVALID 24-AUG-2011 13:41:44
Oracle Data Mining 10.2.0.5.0 INVALID 24-AUG-2011 13:41:44
6 rows selected.
Looks like it VALIDed
Oracle Application Express 3.2.0.00.27 VALID 01-JUN-2013 10:23:35
BUT, XDB is still INVALID
Looking at second link....
ASKER
Second one took car of 4 more!
But not the one I needed to Upgrade APEX... Oracle XML Database
What do you suggest next? Look at the errors?
I am going see how to look at the errors -- IF you know please post it :)
COMP_NAME VERSION STATUS MODIFIED
--------------------------
Oracle Text 10.2.0.5.0 INVALID 01-JUN-2013 10:45:33
Oracle XML Database 10.2.0.5.0 INVALID 01-JUN-2013 10:45:35
Here is what I've done so far:
SQL>sqlplus / as sysdba
SQL>drop table plan_table;
SQL>@?/rdbms/admin/utlxpla
SQL>@?/rdbms/admin/prvtspa
SQL>@?/rdbms/admin/utlrp.s
=====================
OUTPUT BELOW
=====================
SQL> desc plan_table
SQL> drop table plan_table;
Table dropped.
SQL> @?/rdbms/admin/utlxplan
Table created.
SQL> @?/rdbms/admin/prvtspao.pl
PL/SQL procedure successfully completed.
Package created.
No errors.
Synonym created.
No errors.
Package body created.
No errors.
SQL> @?/rdbms/admin/utlrp.sql
SQL> @?/rdbms/admin/utlrp.sql
TIMESTAMP
--------------------------
COMP_TIMESTAMP UTLRP_BGN 2013-06-01 10:31:48
DOC> The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC> objects in the database. Recompilation time is proportional to the
DOC> number of invalid objects in the database, so this command may take
DOC> a long time to execute on a database with a large number of invalid
DOC> objects.
DOC>
DOC> Use the following queries to track recompilation progress:
DOC>
DOC> 1. Query returning the number of invalid objects remaining. This
DOC> number should decrease with time.
DOC> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC> 2. Query returning the number of objects compiled so far. This number
DOC> should increase with time.
DOC> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC> This script automatically chooses serial or parallel recompilation
DOC> based on the number of CPUs available (parameter cpu_count) multiplied
DOC> by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC> On RAC, this number is added across all RAC nodes.
DOC>
DOC> UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC> recompilation. Jobs are created without instance affinity so that they
DOC> can migrate across RAC nodes. Use the following queries to verify
DOC> whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC> 1. Query showing jobs created by UTL_RECOMP
DOC> SELECT job_name FROM dba_scheduler_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC> 2. Query showing UTL_RECOMP jobs that are running
DOC> SELECT job_name FROM dba_scheduler_running_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#
PL/SQL procedure successfully completed.
TIMESTAMP
--------------------------
COMP_TIMESTAMP UTLRP_END 2013-06-01 10:45:30
PL/SQL procedure successfully completed.
DOC> The following query reports the number of objects that have compiled
DOC> with errors (objects that compile with errors have status set to 3 in
DOC> obj$). If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#
OBJECTS WITH ERRORS
-------------------
69
DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#
ERRORS DURING RECOMPILATION
--------------------------
48
FAILED CHECK FOR PACKAGE BODY DRVDML
But not the one I needed to Upgrade APEX... Oracle XML Database
What do you suggest next? Look at the errors?
I am going see how to look at the errors -- IF you know please post it :)
COMP_NAME VERSION STATUS MODIFIED
--------------------------
Oracle Text 10.2.0.5.0 INVALID 01-JUN-2013 10:45:33
Oracle XML Database 10.2.0.5.0 INVALID 01-JUN-2013 10:45:35
Here is what I've done so far:
SQL>sqlplus / as sysdba
SQL>drop table plan_table;
SQL>@?/rdbms/admin/utlxpla
SQL>@?/rdbms/admin/prvtspa
SQL>@?/rdbms/admin/utlrp.s
=====================
OUTPUT BELOW
=====================
SQL> desc plan_table
SQL> drop table plan_table;
Table dropped.
SQL> @?/rdbms/admin/utlxplan
Table created.
SQL> @?/rdbms/admin/prvtspao.pl
PL/SQL procedure successfully completed.
Package created.
No errors.
Synonym created.
No errors.
Package body created.
No errors.
SQL> @?/rdbms/admin/utlrp.sql
SQL> @?/rdbms/admin/utlrp.sql
TIMESTAMP
--------------------------
COMP_TIMESTAMP UTLRP_BGN 2013-06-01 10:31:48
DOC> The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC> objects in the database. Recompilation time is proportional to the
DOC> number of invalid objects in the database, so this command may take
DOC> a long time to execute on a database with a large number of invalid
DOC> objects.
DOC>
DOC> Use the following queries to track recompilation progress:
DOC>
DOC> 1. Query returning the number of invalid objects remaining. This
DOC> number should decrease with time.
DOC> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC> 2. Query returning the number of objects compiled so far. This number
DOC> should increase with time.
DOC> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC> This script automatically chooses serial or parallel recompilation
DOC> based on the number of CPUs available (parameter cpu_count) multiplied
DOC> by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC> On RAC, this number is added across all RAC nodes.
DOC>
DOC> UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC> recompilation. Jobs are created without instance affinity so that they
DOC> can migrate across RAC nodes. Use the following queries to verify
DOC> whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC> 1. Query showing jobs created by UTL_RECOMP
DOC> SELECT job_name FROM dba_scheduler_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC> 2. Query showing UTL_RECOMP jobs that are running
DOC> SELECT job_name FROM dba_scheduler_running_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#
PL/SQL procedure successfully completed.
TIMESTAMP
--------------------------
COMP_TIMESTAMP UTLRP_END 2013-06-01 10:45:30
PL/SQL procedure successfully completed.
DOC> The following query reports the number of objects that have compiled
DOC> with errors (objects that compile with errors have status set to 3 in
DOC> obj$). If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#
OBJECTS WITH ERRORS
-------------------
69
DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#
ERRORS DURING RECOMPILATION
--------------------------
48
FAILED CHECK FOR PACKAGE BODY DRVDML
ASKER
Anymore ideas? Did I lose you?
ASKER
Didn't follow it through
https://forums.oracle.com/forums/thread.jspa?threadID=992817