【Oracle】PSU升级过程

以下是该PSU的自述文件中的内容：

3.2 Patch Installation Instructions

Follow these steps:

  1. If you are using a Data Guard Physical Standby database, you must install this patch on both the primary database and the physical standby database, as described by My Oracle Support Note 278641.1.
  2. Do one of the following, depending on whether this is a RAC environment:
    • If this is a RAC environment, choose one of the patch installation methods provided by OPatch (rolling, all node, or minimum downtime), and shutdown instances and listeners as appropriate for the installation method selected.

      This PSU patch is rolling RAC installable. Refer to My Oracle Support Note 244241.1 Rolling
      Patch - OPatch Support for RAC.

    • If this is not a RAC environment, shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator‘s
      Guide.
  3. Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands: 
    unzip p12419378_11201_<platform>.zip
cd 12419378
opatch apply
  4. If there are errors, refer to Section 5, "Known Issues".

3.3 Patch Post-Installation Instructions

After installing the patch, perform the following actions:

  1. Apply conflict resolution patches as explained in Section 3.3.1.
  2. Load modified SQL files into the database, as explained in Section
    3.3.2.

3.3.1 Applying Conflict Resolution Patches

Apply the patch conflict resolution one-off patches that were determined to be needed when you performed the steps in Section
3.1.4, "One-off Patch Conflict Detection and Resolution".

3.3.2 Loading Modified SQL Files into the Database

The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node.

  1. For each database instance running on the Oracle home being patched, connect to the database using SQL*Plus. Connect as SYSDBA and run the catbundle.sql script
    as follows:

    cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle.sql psu apply
SQL> QUIT

    The catbundle.sql execution is reflected in the dba_registry_history view by a row associated with bundle series PSU.

    For information about the catbundle.sql script, see My Oracle Support Note 605795.1 Introduction
    to Oracle Database catbundle.sql.

  2. Check the following log files in $ORACLE_HOME/cfgtoollogs/catbundle for any errors: 
    catbundle_PSU_<database SID>_APPLY_<TIMESTAMP>.log
catbundle_PSU_<database SID>_GENERATE_<TIMESTAMP>.log

    where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section
    5, "Known Issues".

具体操作过程如下：

解压升级包：

[[email protected] soft]$ unzip p12419378_112010_LINUX\ .zip

进行检查：

[[email protected] soft]$ opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./12419378

Oracle Interim Patch Installer version 11.2.0.3.6

Copyright (c) 2013, Oracle Corporation.  All rights reserved.

PREREQ session

Oracle Home       : /u01/app/oracle/product/11.2.0/dbhome_1

Central Inventory : /u01/app/oraInventory

from           : /u01/app/oracle/product/11.2.0/dbhome_1/oraInst.loc

OPatch version    : 11.2.0.3.6

OUI version       : 11.2.0.1.0

Log file location : /u01/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/opatch2014-09-24_13-04-16PM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.

关闭数据库：

[[email protected] ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Wed Sep 24 12:34:18 2014

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

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

[email protected]>shutdown immediate;

Database closed.

Database dismounted.

ORACLE instance shut down.

升级PSU：

[[email protected] 12419378]$ opatch apply

Oracle Interim Patch Installer version 11.2.0.3.6

Copyright (c) 2013, Oracle Corporation.  All rights reserved.

Oracle Home       : /u01/app/oracle/product/11.2.0/dbhome_1

Central Inventory : /u01/app/oraInventory

from           : /u01/app/oracle/product/11.2.0/dbhome_1/oraInst.loc

OPatch version    : 11.2.0.3.6

OUI version       : 11.2.0.1.0

Log file location : /u01/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/12419378_Sep_24_2014_12_35_57/apply2014-09-24_12-35-57PM_1.log

Applying interim patch ‘12419378‘ to OH ‘/u01/app/oracle/product/11.2.0/dbhome_1‘

Verifying environment and performing prerequisite checks...

Patch 12419378: Optional component(s) missing : [ oracle.client, 11.2.0.1.0 ]

All checks passed.

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:  Y

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = ‘/u01/app/oracle/product/11.2.0/dbhome_1‘)

Is the local system ready for patching? [y|n]

y

User Responded with: Y

Backing up files...

Patching component oracle.rdbms.rsf, 11.2.0.1.0...

Patching component oracle.rdbms.dbscripts, 11.2.0.1.0...

Patching component oracle.rdbms, 11.2.0.1.0...

Patching component oracle.oraolap, 11.2.0.1.0...

Patching component oracle.rdbms.deconfig, 11.2.0.1.0...

Patching component oracle.javavm.server, 11.2.0.1.0...

Patching component oracle.precomp.common, 11.2.0.1.0...

Patching component oracle.network.rsf, 11.2.0.1.0...

Patching component oracle.network.listener, 11.2.0.1.0...

Patching component oracle.rdbms.dv.oc4j, 11.2.0.1.0...

Patching component oracle.sdo.locator, 11.2.0.1.0...

Patching component oracle.sysman.console.db, 11.2.0.1.0...

Patching component oracle.sysman.oms.core, 10.2.0.4.2...

Patching component oracle.rdbms.dv, 11.2.0.1.0...

Patching component oracle.xdk.rsf, 11.2.0.1.0...

Patching component oracle.ldap.rsf.ic, 11.2.0.1.0...

Patching component oracle.ldap.rsf, 11.2.0.1.0...

Patching component oracle.sysman.plugin.db.main.repository, 11.2.0.1.0...

Verifying the update...

Patch 12419378 successfully applied

Log file location: /u01/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/12419378_Sep_24_2014_12_35_57/apply2014-09-24_12-35-57PM_1.log

OPatch succeeded.

[[email protected] ~]$ cd $ORACLE_HOME/rdbms/admin

[[email protected] admin]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Wed Sep 24 12:52:56 2014

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

Connected to an idle instance.

[email protected]>startup

ORACLE instance started.

Total System Global Area  849530880 bytes

Fixed Size                  1339824 bytes

Variable Size             708841040 bytes

Database Buffers          134217728 bytes

Redo Buffers                5132288 bytes

Database mounted.

Database opened.

[email protected]>@catbundle.sql psu apply

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

Generating apply and rollback scripts...

Check the following file for errors:

/u01/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/catbundle/catbundle_PSU_ORCL_GENERATE_2014Sep24_12_56_54.log

Apply script: /u01/app/oracle/product/11.2.0/dbhome_1/rdbms/admin/catbundle_PSU_ORCL_APPLY.sql

Rollback script: /u01/app/oracle/product/11.2.0/dbhome_1/rdbms/admin/catbundle_PSU_ORCL_ROLLBACK.sql

PL/SQL procedure successfully completed.

Executing script file...

略。。。。。。

Check the following log file for errors:

/u01/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/catbundle/catbundle_PSU_ORCL_APPLY_2014Sep24_12_56_54.log

至此PSU升级完毕

时间： 2024-10-01 19:34:48

【Oracle】PSU升级过程的相关文章

ORACLE PSU升级总结

首先,进行PSU,首要的事情就是认真的看readme.html,从里面我们可以知道很详细的升级步骤已经回退的方案.并且避免了很多的坑 在进行PSU之前,要首先确认你准备升级的版本以及你自己系统数据库的版本,就像我们这次,是从11.2.0.4.0升级到11.2.0.4.2版本,从MOS上去找到相应的PATCH p18031668_112040_Linux-x86-64.zip 可以通过p后面的数字在mos上面很容易的查到该补丁包,从该版本的补丁包的readme.html 中.我们可以看到这样要求

oracle数据库psu升级（本实验是将10.2.0.3.12升级到10.2.0.3.15）

psu升级(本实验是将10.2.0.3.12升级到10.2.0.3.15) 一.解压安装包自定义存放路径为/home/oracle/yjb/psu/10.2.0.3.15cd /home/oracle/yjb/psu/10.2.0.3.15unzip p6880880_112000_04-SEP-2015_Linux-x86-64.zipunzip p20760997_112030_15_Linux-x86-64.zip -d 1120315 二.检查psu补丁是否有冲突/home/oracle

Oracle升级_oracle 10g版本由 10.2.0.4.0升级为10.2.0.4.4（即PSU升级）

***************************************************************************************************** 续借上篇:Oracle升级_oracle 10g版本由 10.2.0.1.0升级为10.2.0.4.0(即CPU升级) ***********************************************声明***************************************

Oracle Study之--Oracle TimeZone升级

Oracle Study之--Oracle TimeZone升级 http://tiany.blog.51cto.com/513694/1411882  Oracle 10gR2升级到Oracle 11gR2       当Oracle database从10gR2升级到11gR2之后,需要升级timezone version,以下详细介绍了timezone的升级过程. Oracle timezone 升级 背景描述: 如果需要支持一个国际化的应用,那么数据库端的国际化特性的支持也就显得尤其重要

一次误操作导致的gi psu升级失败

oracle使用opatch auto的方式安装gi psu时需要一个节点一个节点来,昨晚的升级中,因为误操作而是两节点同时安装gi psu,最终在补丁安装完成后,无法拉起crs. 选择进行补丁的rollback,结果悲剧的发现rollback的前提是需要crs启动的状态,无奈之下只能进行备份文件的恢复了. 不过因为意识的疏忽,压缩$oracle_home目录和$grid_home目录时没有使用root用户,导致部分文件没有备份出来. 以后打类似的psu,有两个注意点: 第一,一定要一个节点一个

Oracle RAC安装过程中碰到的“坑”和关键点(二)

(1) 依赖包的安装 Linux下安装Oracle,除了系统配置参数,我觉得依赖包的安装是另一个比较琐碎的操作. 本次安装碰到了几个包的问题: (a) rpm -Uvh gcc-4*提示: 02. error: Failed dependencies: 03.    cloog-ppl >= 0.15 is needed by gcc-4.4.7-4.el6.x86_64 04.    cpp = 4.4.7-4.el6 is needed by gcc-4.4.7-4.el6.x86_64 不

Windows平台下Oracle实例启动过程中日志输出

Windows平台下Oracle实例启动过程中日志输出记录. 路径:D:\app\Administrator\diag\rdbms\orcl\orcl\trace\alert_orcl.log 输出内容: Sat Aug 06 20:39:55 2016 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 3 Usin

通过 yum update 将系统从CentOS 6.2 升级到 CentOS 6.6 及升级过程中的简单排错

本文说明 本文写于2014年的WP中,后WP停止维护,今天翻到此记录整理下,记录于此,方便日后查看. 话说那时候写博客真是认真啊~哈哈~ 升级前的系统信息 [[email protected] ~]# uname -a Linux thatsit 2.6.32-220.el6.x86_64 #1 SMP Tue Dec 6 19:48:22 GMT 2011 x86_64 x86_64 x86_64 GNU/Linux [[email protected] ~]# uname -r 2.6.32

Unity5.x 项目升级过程中常见问题解决方案总结

最近整理Unity4.x 项目升级Unity5.0 过程中出现的各种常见问题,与大家共享. 1:Unity4.x 项目中3D模型其材质丢失,成为"白模"?      解决方案:手工重新赋值材质贴图. 2:Unity4.x 项目中的NavMesh 升级报错?     "NavMesh asset format has changed. Please rebake the NavMesh data." ?     解决方案:按照字面含义,重新对静态物体进行烘焙即可. 3