linux平台下oracle从10.2.0.1升级到10.2.0.4

最新推荐文章于 2024-09-20 11:12:39 发布

cyxlxp8411

最新推荐文章于 2024-09-20 11:12:39 发布

阅读量1.2k

点赞数

分类专栏： Oracle 基础知识文章标签： oracle linux 平台 database constraints manager

Oracle 基础知识专栏收录该内容

110 篇文章 0 订阅

订阅专栏

10.1.0.X.0 TO 10.2.0.4.0
1. Install 10.2.0.1.0 software
The software can be downloaded from the following link :
http://www.oracle.com/technology/software/products/database/index.html
https://metalink2.oracle.com/metalink/plsql/showdoc?db=NOT&id=169706.1&blackframe=1 : Oracle? Database Installation and Configuration Requirements Quick Reference (8.0.5 to 11.1)

2. Install the 10.2.0.4.0 patchset on top of 10.2.0.1.0 ORACLE_HOME Patchset number is : 6810189
http://updates.oracle.com/download/6810189.html

3. Upgrade the database to 10.2.0.4.0
https://metalink2.oracle.com/metalink/plsql/showdoc?db=NOT&id=419550.1&blackframe=1 : Different Upgrade Methods For Upgrading Your Database
https://metalink2.oracle.com/metalink/plsql/showdoc?db=NOT&id=316889.1&blackframe=1 : Complete checklist for manual upgrades to 10gR2

REFERENCE:
List of fixes included in 10.2.0.4 https://metalink2.oracle.com/metalink/plsql/showdoc?db=NOT&id=401436.1&blackframe=1
Known issues and alerts affecting 10.2.0.4 https://metalink2.oracle.com/metalink/plsql/showdoc?db=NOT&id=555579.1&blackframe=1

升级过程:
1.如果是全新安装的数据库,直接运行补丁包就可以了
p6810189_10204_Linux-x86.zip
./runInstaller

2.如果是已经创建了数据库,并且有应用在上面,则先停止相关应用
再按以下步骤执行:
0)shutdown 数据库,并停止所有oracle相关的服务和stop listener .
    $ isqlplusctl stop
    $ emctl stop dbconsole
    $ lsnrctl stop
注意：需要停止Distributed Transaction Coordinator服务/iis服务/web publish(www)/;
1)冷备份数据库
2)运行安装补丁程序
3)startup upgrade;   lsnrctl start
   #3.1)修改java_pool_size / large_pool_size=150M

# 10g的sga自动分配，所以不需要修改 java_pool_size 和 large_pool_size

4)运行脚本@rdbms/admin/catupgrd.sql

# @rdbms/admin/catalog.sql;
# @rdbms/admin/catproc.sql;

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP RUL 2012-05-16 21:41:15
DBUA_TIMESTAMP RUL VALID 2012-05-16 21:41:15

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UPGRD_END 2012-05-16 21:42:24
.
Oracle Database 10.2 Upgrade Status Utility           05-16-2012 21:42:24
.
Component                                Status         Version HH:MM:SS
Oracle Database Server                    VALID      10.2.0.5.0 00:05:32
JServer JAVA Virtual Machine              VALID      10.2.0.5.0 00:01:42
Oracle XDK                                VALID      10.2.0.5.0 00:00:20
Oracle Database Java Packages             VALID      10.2.0.5.0 00:00:17
Oracle Text                               VALID      10.2.0.5.0 00:00:23
Oracle XML Database                       VALID      10.2.0.5.0 00:01:35
Oracle Workspace Manager                  VALID      10.2.0.5.0 00:00:33
Oracle Data Mining                        VALID      10.2.0.5.0 00:00:12
OLAP Analytic Workspace                   VALID      10.2.0.5.0 00:00:15
OLAP Catalog                              VALID      10.2.0.5.0 00:00:33
Oracle OLAP API                           VALID      10.2.0.5.0 00:00:37
Oracle interMedia                         VALID      10.2.0.5.0 00:03:02
Spatial                                   VALID      10.2.0.5.0 00:01:30
Oracle Expression Filter                  VALID      10.2.0.5.0 00:00:11
Oracle Enterprise Manager                 VALID      10.2.0.5.0 00:00:50
Oracle Rule Manager                       VALID      10.2.0.5.0 00:00:06
.
Total Upgrade Time: 00:18:56
DOC>#######################################################################
DOC>#######################################################################
DOC>
DOC>   The above PL/SQL lists the SERVER components in the upgraded
DOC>   database, along with their current version and status.
DOC>
DOC>   Please review the status and version columns and look for
DOC>   any errors in the spool log file. If there are errors in the spool
DOC>   file, or any components are not VALID or not the current version,
DOC>   consult the Oracle Database Upgrade Guide for troubleshooting
DOC>   recommendations.
DOC>
DOC>   Next shutdown immediate, restart for normal operation, and then
DOC>   run utlrp.sql to recompile any invalid application objects.
DOC>
DOC>#######################################################################
DOC>#######################################################################
DOC>#
SQL>
SQL>
SQL>
SQL> show user
USER is "SYS"

5)shutdown immediate
6)startup
7)运行脚本@rdbms/admin/utlrp.sql;

SQL> @rdbms/admin/utlrp.sql

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN 2012-05-16 21:54:40
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>#

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_END 2012-05-16 21:55:27
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
SQL>

8)--察看数据库安装的组件、版本、状态:
     col comp_name format a30
     col version format a30
     col status format a10
     SELECT comp_name, version, status  FROM dba_registry;

SQL> col comp_name format a30
SQL> col version format a30
SQL> col status format a10
SQL> select comp_name,version,status from dba_registry;

COMP_NAME                      VERSION                        STATUS
------------------------------ ------------------------------ ----------
Oracle Enterprise Manager      10.2.0.5.0                     VALID
Spatial                        10.2.0.5.0                     VALID
Oracle interMedia              10.2.0.5.0                     VALID
OLAP Catalog                   10.2.0.5.0                     VALID
Oracle XML Database            10.2.0.5.0                     VALID
Oracle Text                    10.2.0.5.0                     VALID
Oracle Expression Filter       10.2.0.5.0                     VALID
Oracle Rule Manager            10.2.0.5.0                     VALID
Oracle Workspace Manager       10.2.0.5.0                     VALID
Oracle Data Mining             10.2.0.5.0                     VALID
Oracle Database Catalog Views 10.2.0.5.0                     VALID
Oracle Database Packages and T 10.2.0.5.0                     VALID
ypes

JServer JAVA Virtual Machine   10.2.0.5.0                     VALID
Oracle XDK                     10.2.0.5.0                     VALID
Oracle Database Java Packages 10.2.0.5.0                     VALID
OLAP Analytic Workspace        10.2.0.5.0                     VALID
Oracle OLAP API                10.2.0.5.0                     VALID
SQL>

PS:
Chmod -R 777 /u01 -->改变权限
Chmod oracle /u01 -->改变文档所有者
When I execute the runInstaller for the patchset it gives me:

Checking operating system version: must be redhat-3, SuSE-9, SuSE-10, redhat-4, redhat-5, UnitedLinux-1.0, asianux-1, asianux-2 or asianux-3
Failed <<<<

I already had set /etc/redhat-release to:
redhat-5
What needs editing is these files:

/etc/issue
/etc/issue.net
/etc/redhat-release

In those files you will put this:

Red Hat Enterprise Linux Server release 5 (Tikanga)
Kernel /r on an /m

"Tikanga" is for 5.0 only If your running 5.1 you need to substitute the name for it. The same applys to also CentOS version 4, you substitute the appropriate line.

After your Oracle DB or Oracle App is installed change them back.

an other way to resolve this is to use the switch

-ignoreSysPrereqs

when starting the installer