探索Oracle之数据库升级六11.2.0.4.3Upgrade12c(12.2.0.1) - 数据库编程

owing error: DOC> DOC> select dbms_java.longname(\'foo\') \"JAVAVM TESTING\" from dual DOC> * DOC> ERROR at line 1: DOC> ORA-00904: \"DBMS_JAVA\".\"LONGNAME\": invalid identifier DOC> DOC> If the JAVAVM component is installed, the query should succeed DOC> with \'foo\' as result. DOC> DOC>################################################################# DOC># JAVAVM TESTING --------------- foo =================================== Oracle Multimedia/InterMedia status =================================== . Oracle Multimedia/interMedia is installed and listed with the following version: 11.2.0.4.0 and status: VALID . Checking for installed Database Schemas... ORDSYS user exists. ORDPLUGINS user exists. MDSYS user exists. SI_INFORMTN_SCHEMA user exists. ORDDATA user exists. . Checking for Prerequisite Components... JAVAVM installed and listed as valid XDK installed and listed as valid XDB installed and listed as valid Validating Oracle Multimedia/interMedia...(no output if component status is valid) PL/SQL procedure successfully completed. *** End of LogFile *** not spooling currently Enter value for log_path: /home/oracle/diag/ Upload db_upg_diag_woo_20_Nov_2014_0504.log from \"/home/oracle/diag\" directory SQL> exit

4.4 升级前检查无效对象:

[oracle@db01 ~]$ cd $ORACLE_HOME/rdbms/admin 
[oracle@db01 admin]$ sqlplus / as sysdba @utlrp.sql

SQL*Plus: Release 11.2.0.4.0 Production on Thu Nov 20 06:13:55 2014
Copyright (c) 1982, 2013, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN 2014-11-20 06:13:56

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_REC

探索Oracle之数据库升级六11.2.0.4.3Upgrade12c(12.2.0.1)(八)