在虚拟机上升级oracle从 10.2.0.1.0 到10.2.0.5.0

[oracle@orahost ~]$ sqlplus / as sysdba

SQL*Plus: Release 10.2.0.1.0 - Production on Mon Jul 15 17:52:41 2013

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to an idle instance.

进入图形界面中。

首先，将数据库关闭，包括监听和所有连接等。

将补丁文件上传 p8202632_10205_LINUX.zip

解压后，进入Disk1 执行

[root@orahost Disk1]# xhost +

su -oracle

./runInstaller 

因为我的是单实例的，所以只是upgrade oracle软件就可以。

根据提示：最后以root身份执行：

[root@orahost ~]# cd /oracle/product/10.2.0/db_1/
[root@orahost db_1]# sh root.sh
Running Oracle 10g root.sh script...


The following environment variables are set as:
    ORACLE_OWNER= oracle
    ORACLE_HOME=  /oracle/product/10.2.0/db_1


Enter the full pathname of the local bin directory: [/usr/local/bin]: 
   Copying dbhome to /usr/local/bin ...
   Copying oraenv to /usr/local/bin ...
   Copying coraenv to /usr/local/bin ...


Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.

将oracle软件升级后，

[oracle@orahost ~]$ sqlplus / as sysdba


SQL*Plus: Release 10.2.0.5.0 - Production on Wed Jul 17 15:46:18 2013


Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.


Connected to an idle instance.

SQL>  startup upgrade

SQL> @?/rdbms/admin/catupgrd.sql

内容略。。。。。。

SQL> select status from v$instance;


STATUS
------------
OPEN MIGRATE
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.

SQL*Plus: Release 10.2.0.5.0 - Production on Wed Jul 17 15:46:18 2013


Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.


Connected to an idle instance.


SQL> startup
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.


Total System Global Area 1077936128 bytes
Fixed Size    1277824 bytes
Variable Size  314572928 bytes
Database Buffers  754974720 bytes
Redo Buffers    7110656 bytes
Database mounted.
Database opened.

SQL> @?/rdbms/admin/utlrp.sql

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN  2013-07-17 16:00:04


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-07-17 16:01:11




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
-------------------
 0


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
---------------------------
 0




PL/SQL procedure successfully completed.


SQL>