【PSU】AIX Oracle 11g RAC自动打GI PSU5补丁(11.2.0.3.5)

前言部分

导读和注意事项

各位技术爱好者，看完本文后，你可以掌握如下的技能，也可以学到一些其它你所不知道的知识，~O(∩_∩)O~：

① 升级PSU的一般性方法（重点）

② PSU/CPU/PATCHSET等的一些相关概念

③ 如何查看oracle的PSU，如何在MOS上找到想要的patch号

相关知识点扫盲

每个数据库版本都有自己的PSU，PSU版本号体现在数据库版本的最后一位，MOS站点中Oracle Recommended Patches — Oracle Database [ID 756671.1] 文档中查到各个产品版本最新的PSU。

PSU (Patch Set Updates)

PSU(补丁集更新)是累积型补丁--即某个特定的补丁集，它先前所有的PSU被包含于最近的PSU中，例如：11.2.0.3.11的所有bug修复被包含于11.2.0.3.12中。PSU包含推荐的bug修复，及最近的CPU，PSU每个季度发布一次。

Oracle对于其产品每个季度发行一次的补丁包，包含了bug的修复。Oracle选取被用户下载数量多的，并且被验证过具有较低风险的补丁放入到每个季度的PSU中。在每个PSU中不但包含Bug的修复而且还包含了最新的CPU。

CPU: Critical Patch Update （SPU: Security Patch Update）

Oracle对于其产品每个季度发行一次的安全补丁包，通常是为了修复产品中的安全隐患。

Upgrade与Update

首先，我们针对所使用的数据库可能会进行如下措施，版本升级或补丁包升级，那何为版本升级、何为补丁包升级呢？

比如我的当前数据库是10GR2版本，但公司最近有个升级计划，把这套数据库升级到当下最新的11GR2，这种大版本间升级动作即为Upgrade。根据公司计划在原厂工程师和DBA共同努力下，数据库已升级到11GR2，当下版本为11.2.0.3.0。这时候原厂工程师推荐把最新的PSU给打上，获得老板的批准之后，我们又把数据库进行补丁包的升级，应用了PSU Patch14727310之后，数据库版本现在成为11.2.0.3.5，这个过程即是Update。

不得不再次提醒，Upgrade和Update都希望在获得原厂的支持下进行，尤其是Upgrade，这对于企业来说是个非常大的动作！

MOS对概念的解释

Generally patches for Clusterware, Grid Infrastructure and/or the Database are catagorized into the following:

• Patchsets
• Patchset Updates (PSUs)
• Critical Patch Updates (CPUs)
• Bundle Patches
• Interim (one-off) Patches

Patchsets Q&A

What's a Patchset?

Compared to all other patch types, a Patchset is released the least frequently. It contains fixes for most known issues for the release and potentially also introduces new features. A patchset is cumulative and when applied it changes the fourth digit of the product release banner - for example, 10.2.0.5 is 4th patch set for 10.2, and 11.2.0.2 is the 1st patch set for 11.2.

A patchset must be installed via the Oracle Universal Installer (OUI) and is generally considered an "upgrade".

Prior to 11gR2, a base release had to be installed before a patchset could be applied. For example, to install 10.2.0.5 on Linux, the 10.2.0.1 base release has to be installed first and then upgraded to 10.2.0.5.

Prior to 11gR2, the same patchset download is used to patch the Clusterware, ASM and Database homes. For example, Patch 8202632 is the 10.2.0.5 patchset, this same patch (Patch 8202632) will be used to patch the 10.2.0.x Clusterware, 10.2.0.x ASM and 10.2.0.x Database to 10.2.0.5.

Starting with 11gR2, patchset releases are now full releases and no longer require a "base" release, e.g. 11.2.0.2 can be installed directly without having to install 11.2.0.1 first.

Prior to 11gR2 - even though the CRS and RDBMS base releases were provided on separate media (downloadable zip file or separate DVD/CD) - the patchsets for both products were delivered as one i.e. the same patchset could be applied to the CRS as well as the RDBMS home.

Starting with 11gR2 the patchsets for Grid Infrastructure and RDBMS are delivered separately (as they are full releases).

Clusterware patchsets can be applied in a rolling fashion, while database patchsets cannot. For example, you can rolling upgrade clusterware to 11.2.0.2, but you have to shutdown database on all nodes to upgrade to database 11.2.0.2.

Patch Set Updates (PSUs) Q&A

What's a Patch Set Update (PSU)?

As the name implies PSUs are patches that are applied on top of a given patchset release. They are released on a quarterly basis and contain fixes for known critical issues for the patchset. PSUs are subject to thorough testing and do not include changes that would alter the functionality of the software. With this in mind, PSUs are designed to provide "low risk" and "high value" allowing for customers to more easily adopt proactive patching strategies. Consider the following PSU facts:

• All PSUs are installed via "opatch" and are not considered an "upgrade".
• Database PSUs always contain the CPU for the respective quarter that the PSU is released in. PSUs and CPUs are NOT compatible meaning if you apply the 11.2.0.2.2 Database PSU and then want to apply the 11.2.0.2 July CPU this would result in the rollback of the 11.2.0.2.2 Database PSU. That said, once a PSU patching strategy is adopted it must be maintained.
• Independent PSUs are released for both the Database and Clusterware or Grid Infrastructure installations.
  • Clusterware PSUs (pre-11.2) are refered to as CRS PSUs
  • Grid Infrastructure PSUs are refered to as GI PSUs
    • GI PSUs do contain the Database PSU for the corresponding release, e.g. 11.2.0.2.3 GI PSU contains the 11.2.0.2.3 Database PSU
  • Database PSUs hold true to their name
• Both Clusterware/Grid Infrastructure and Database PSU patches are cumulative. Clusterware PSU refers to CRS PSU for pre-11gR2 and GI PSU for 11gR2.
• GI PSUs are always cumulative meaning that you can apply higher version GI PSU directly without having to apply a lower version one first. For example, the 11.2.0.2.2 GI PSU can be applied to a 11.2.0.2 home without having to apply GI PSU 11.2.0.2.1 first.
• Database PSUs can be subject to overlay PSU packaging. In these cases, the PSUs are still cumulative, but a higher PSU may require a lower PSU to be applied first; for example, to apply database PSU 10.2.0.4.7, you must apply database PSU 10.2.0.4.4 first. If a previous PSU is a prerequisite to a later PSU the requirement will be clearly documented in the PSU readme.
• For more information on PSUs please review Document 854428.1.

What's the PSU release schedule?

Generally speaking PSU are released on quarterly basis for both Clusterware/Grid Infrastructure and Database. There's cases where a Clusterware PSUs is not released for corresponding Database PSU. For example, there's database PSU 10.2.0.5.4 but no CRS PSU 10.2.0.5.4.

Will the 5th digit of the version be changed after PSU is applied?

A PSU will not physically update the 5th-digit of the release information, the updates to the 5th digit in the release are for Documentation purposes only. So the third GI PSU that was released for 11.2.0.2 will have a documentation version of 11.2.0.2.3. You will NOT see this change reflected in the actual software version if you query it from the inventory, clusterware or database.

What's included in a GI PSU ?

Unlike other Grid Infrastructure patches (discussed later), 11gR2 GI PSUs contains both GI PSU and Database PSU (YES, both GI and DB PSU) for a particular quarter. For example, 11.2.0.2.2 GI PSU contains both the 11.2.0.2.2 GI PSU and the 11.2.0.2.2 Database PSU.

You are able to take note of this when you extract a GI PSU, you will see 2 directories (named with the Patch number) one for the GI PSU and one for the RDBMS PSU.

How do I find out whether a bug is fixed in a Clusterware or Grid Infrastructure PSU ? To find out, check the patch readme and the following notes:

Document 405820.1 - 10.2 CRS PSU Known issues
Document 810663.1 - 11.1 CRS PSU Known issues
Document 1082394.1 - 11.2.0.1 GI PSU Known issues

Document 1272288.1 - 11.2.0.2 GI PSU Known Issues
Document 1508641.1 - 11.2.0.3.x Grid Infrastructure Bundle/PSU Known Issues

Once the GI PSU is applied, "opatch lsinventory" will show that both GI PSU and DB PSU are applied, i.e.:

Interim patches (2) :

Patch 9654983 : applied on Thu Feb 02 20:36:47 PST 2012
Patch 9655006 : applied on Thu Feb 02 20:35:53 PST 2012

And "opatch lsinventory -bugs_fixed" will list each individual bugs that have been fixed by all installed patches, i.e.:

List of Bugs fixed by Installed Patches:

Bug Fixed by Installed at Description
Patch
--- -------- ------------ -----------

7519406 9654983 Thu Feb 02 20:36:47 PST 2012 'J000' TRACE FILE REGARDING GATHER_STATS_JOB INTER
..
9783609 9655006 Thu Feb 02 20:35:53 PST 2012 CRS 11.2.0.1.0 Bundle

Can a Database PSU be applied to a clusterware home?

No, only CRS PSUs, GI PSUs or other Clusterware/GI patches can be applied to a Clusterware/GI home.

Critical Patch Updates (CPUs) Q&A

What are Critical Patch Updates (CPUs)?

CPU Patches are collection of high-priority fixes for security related issues and are only applicable to the Database Home (and pre-11.2 ASM Home(s)) . CPUs are released quarterly on the same cycle as PSUs and are cumulative with respect to prior security fixes but may contain other fixes in order to address patch conflicts with non-security patches. PSUs always contain the CPU for that respective quarter. PSUs and CPUs are NOT compatible meaning if you apply the 11.2.0.2.2 Database PSU and then want to apply the 11.2.0.2 July CPU this would result in the rollback of the 11.2.0.2.2 Database PSU. That said, once a PSU patching strategy is adopted it must be maintained. PSU patching is preferred over CPU Patching.

Bundle Patches Q&A

What's the difference between a Clusterware/Grid Infrastructure bundle patch and a PSU?

A Clusterware or Grid Infrastructure (GI) patch can be in the form of bundle or Patchset Update (PSU). The biggest difference between a GI/Clusterware bundle and a PSU is that PSUs are bound to a quarterly release schedule while a bundle may be released at any time throughout the course of a given quarter. If a GI/Clusterware bundle is released in a given quarter, the fixes in that bundle will be included in the PSU that will be released for that quarter. This concept allows for development to provide critical bug fixes in a more granular timeline if necessary.

Interim (one-off) Patch Q&A

What's an interim patch (one-off patch)?

An interim patch contains fixes for one or in some cases several bugs (merge patch).

Clusterware interim patches are rare, they usually are build on top of the latest PSU (at the time) and include the entire PSU they were built on.

The same does not hold true for database interim patches, they usually do not include a PSU.

An interim clusterware patch on top of a PSU includes the PSU, for example, 11.2.0.2.2 patch 12647618 includes 11.2.0.2 GI PSU2 (11.2.0.2.2). But the same is not true for database interim patch, for example, 11.2.0.2.2 databasepatch 11890804 can only be applied on top of a 11.2.0.2.2 database home.

General Patch Q&A

What's the difference between Clusterware/Grid Infrastructure patches and Database patches?

Generally speaking Clusterware/Grid Infrastructure patches modify files that belong to the Clusterware or Grid Infrastructure product, while Database patches change files that belong to the database product. As they apply to different sets of files, they do not conflict with each other.

Please note:

• "files" in this context can refer to binaries/executables, scripts, libraries etc
• Clusterware files can reside in all types of Oracle software homes like clusterware home, database home and ASM home
• Prior to 11gR2, RDBMS files reside in DB/ASM homes only, while with 11gR2 RDBMS files will also reside in the GI home (as ASM is now part of GI)
• A GI PSU is a special type of clusterware patch as it also includes a database PSU and modifies database binaries.

安装PSU的一般性步骤

每个PSU安装包中都包含一个README.html或README.TXT文档，其中描述了如何安装该PSU，有些PSU是可以直接安装的，而有些PSU则必须要求安装了上一个版本的PSU之后才能继续安装。比如对于10.2.0.4版本的数据库来说，PSU 10.2.0.4.4可以直接安装在最原始的10.2.0.4.0版本中，而最新的PSU 10.2.0.4.8则必须要求先安装10.2.0.4.4。这些信息在README.html中都可以找到，所以请仔细阅读该文档。

通常安装PSU是比较简单的，步骤如下：

1) 安装PSU需要使用到opatch，在README.html中有描述该PSU需要的最低版本opatch，如果当前opatch版本过低，则需要先下载 Patch 6880880，该Patch中包含最新的opatch，只需要解压覆盖原先的$ORACLE_HOME/OPatch目录即可。

查看当前的opatch版本，可以使用opatch version命令。

$ opatch version

Invoking OPatch 10.2.0.5.2

OPatch Version: 10.2.0.5.2

OPatch succeeded.

2）安装PSU，请仔细阅读README.html，确认安装命令，通常是简单的opatch apply。

$opatch apply

3）更新数据库，将修改过的SQL文件应用到数据库中，很多DBA在执行完上述安装命令以后就不再进行这一步，那么实际上PSU是没有完整安装的。

cd $ORACLE_HOME/rdbms/admin

sqlplus / as sysdba

SQL> STARTUP

SQL> @catbundle.sql psu apply

SQL> QUIT

注意：如果PSU是overlay PSU，比如10.2.0.4.8，则需要执行@catbundle.sql opsu apply，同样这些在README.html中都有详细描述。

如何确认当前数据库已经安装了什么PSU/CPU？

数据库版本 sqlplus -v

检查数据库PSU号命令为su - oracle -> opatch lsinventory

集群数据库

10205版本，CRS为PSU2，补丁号为9952245 | DB有PSU3，补丁号为11724962、DB有PSU6，补丁号为13343471、DB有PSU7，补丁号为13632743

10205版本单库无CRS，只有DB的PSU，如：DB有PSU3，补丁号为11724962、DB有PSU6，补丁号为13343471、DB有PSU7，补丁号为13632743

11G单库或集群都有GI和DB PSU,opatch lsinventory显示具体的PSU号，如:

--------------------------------------------------------------------------------------------------

Patch 13923374 : applied on Tue Sep 04 10:53:32 GMT+08:00 2012

Unique Patch ID: 14912546

Patch description: "Database Patch Set Update : 11.2.0.3.3 (13923374)" ---->DB PSU3补丁

Sub-patch 13696216; "Database Patch Set Update : 11.2.0.3.2 (13696216)" ---->DB PSU2补丁

Sub-patch 13343438; "Database Patch Set Update : 11.2.0.3.1 (13343438)" ---->DB PSU1补丁

Patch 13919095 : applied on Tue Sep 04 10:50:02 GMT+08:00 2012

Unique Patch ID: 14912546

Patch description: "Grid Infrastructure Patch Set Update : 11.2.0.3.3 (13919095)" ---->GI PSU3补丁

---------------------------------------------------------------------------------------------------

上面的例子是11203版本的集群,DB安装了PSU1、PSU2、PSU3，取最大PSU号，即DB为PSU3，PSU3包括PSU2、PSU1，GI为PSU3

不同的版本类推即可！！！

opatch lsinventory -bugs_fixed | grep 'PSU'

opatch lsinv

opatch lspatches

ZFLHRDB1:grid:/home/grid>opatch lspatches

13343438;Database Patch Set Update : 11.2.0.3.1 (13343438)

13348650;Grid Infrastructure Patch Set Update : 11.2.0.3.1 (13348650)

col action_time for a30

col action for a10

col namespace for a10

col version for a10

col bundle_series for a10

col comments for a30

SELECT to_char(action_time, 'YYYY-MM-DD HH24:MI:SS') action_time,

action,

namespace,

version,

id,

bundle_series,

comments

FROM dba_registry_history D;

PSU升级正文部分

准备工作

数据库环境

软件准备

我们需要准备的软件如下表格所示，至于这些内容怎么来的我们不要急，且看下边的MOS上下载安装软件：

说明：GI PSU包括DB PSU,CPU。

MOS上下载安装软件

PSU下载

首先我们登录MOS网站，https://support.oracle.com，然后查找文档号为：**1922396.1**，找到11.2.0.3，如下图所示：

或者文档ID 1922396.1的文件小麦苗已经下载下来了，大家可以去http://blog.itpub.net/26736162/viewspace-1624453进行下载，不止如此，小麦苗还把其他需要阅读的文档也下载下来了，可以去云盘下载。

找到11.2.0.3.5，由于我们是rac环境，所以下载GI PSU即可，所以对应的就是 14727347 (11.2.0.3.5)，如上图中所示，点击相应的连接进入下载页面，然后在右边选择我们需要的平台，AIX 64位，如下图所示：

复制连接地址到迅雷或直接点击即可下载。

接下来就是等PSU下载完成后，我们用2345好压软件或其它解压缩软件打开，把其中的readme.html文件先拿出来，

打开：

该文件即PSU5的安装说明文档，我们接下来安装这个文档来安装就可以了。

OPatch下载

我们从上边的readme.html中得到opatch的最低要求是11.2.0.3.0，而目前我们的版本为11.2.0.1.7，所以需要下载最新版本，下载的地址下图中也有连接即6880880，如图所示：

我们也可以直接去OPatch下载地址：
https://updates.oracle.com/download/6880880.html

https://updates.oracle.com/ARULink/PatchDetails/process_form?patch_num=6880880

打开相应的连接后，需选择我们需要的平台：

接下来下载即可。

上传软件到/softtmp目录并赋权

首先利用SecureFX软件上传下载的文件p14727347_112030_AIX64-5L.zip和p6880880_112000_AIX64-5L.zip到/softtmp目录，然后赋权。

ZHLHRDB1:root:/softtmp>chmod 777 p*

total 2425568

drwxr-xr-x 2 root system 256 May 05 15:31 lost+found

-rwxrwxrwx 1 oracle dba 1187252238 May 17 09:44 p14727347_112030_AIX64-5L.zip

-rwxrwxrwx 1 root system 54636538 May 16 22:13 p6880880_112000_AIX64-5L.zip

更新2个节点的OPatch版本，必须要更新

说明：分别在两个节点更新GRID_HOME和ORACLE_HOME的OPatch版本。

备份OPatch目录

分别对grid和oracle用户下的OPatch目录进行备份：

ZHLHRDB1:root:/softtmp>su - oracle

ZHLHRDB1:oracle:/oracle>echo $ORACLE_HOME

/oracle/app/oracle/product/11.2.0/db

ZHLHRDB1:oracle:/oracle>su - grid

grid's Password:

ZHLHRDB1:grid:/home/grid>echo $ORACLE_HOME

/oracle/app/11.2.0/grid

ZHLHRDB1:root:/softtmp>cp -r /oracle/app/oracle/product/11.2.0/db/OPatch /oracle/app/oracle/product/11.2.0/db/OPatch_bk

ZHLHRDB1:root:/softtmp>cp -r /oracle/app/11.2.0/grid/OPatch /oracle/app/11.2.0/grid/OPatch_bk

grid目录OPatch替换

ZHLHRDB1:root:/softtmp>su - grid

ZHLHRDB1:grid:/home/grid>which opatch

/oracle/app/11.2.0/grid/OPatch/opatch

ZHLHRDB1:grid:/home/grid>opatch version

Invoking OPatch 11.2.0.1.7

OPatch Version: 11.2.0.1.7

OPatch succeeded.

ZHLHRDB1:grid:/home/grid>unzip /softtmp/p6880880_112000_AIX64-5L.zip -d $ORACLE_HOME

Archive: /softtmp/p6880880_112000_AIX64-5L.zip

extracting: /oracle/app/11.2.0/grid/OPatch/version.txt

replace /oracle/app/11.2.0/grid/OPatch/opatch.bat? [y]es, [n]o, [A]ll, [N]one, [r]ename: A

inflating: /oracle/app/11.2.0/grid/OPatch/opatch.bat

inflating: /oracle/app/11.2.0/grid/OPatch/opatchprereqs/opatch/opatch_prereq.xml

inflating: /oracle/app/11.2.0/grid/OPatch/opatchprereqs/opatch/rulemap.xml

inflating: /oracle/app/11.2.0/grid/OPatch/opatchprereqs/opatch/runtime_prereq.xml

《《《《。。。。。。。。篇幅原因，有省略。。。。。。。。》》》》

inflating: /oracle/app/11.2.0/grid/OPatch/oplan/jlib/EMrepoDrivers.jar

inflating: /oracle/app/11.2.0/grid/OPatch/oplan/jlib/bundle.jar

inflating: /oracle/app/11.2.0/grid/OPatch/oplan/README.txt

inflating: /oracle/app/11.2.0/grid/OPatch/opatchdiag

ZHLHRDB1:grid:/home/grid>which opatch

/oracle/app/11.2.0/grid/OPatch/opatch

ZHLHRDB1:grid:/home/grid>opatch version

OPatch Version: 11.2.0.3.12 ====》grid用户的OPatch软件升级成功

OPatch succeeded.

oracle目录OPatch替换

ZHLHRDB1:root:/softtmp>su - oracle

ZHLHRDB1:oracle:/oracle>which opatch

/oracle/app/oracle/product/11.2.0/db/OPatch/opatch

ZHLHRDB1:oracle:/oracle>opatch version

Invoking OPatch 11.2.0.1.7

OPatch Version: 11.2.0.1.7

OPatch succeeded.

ZHLHRDB1:oracle:/oracle>unzip /softtmp/p6880880_112000_AIX64-5L.zip -d $ORACLE_HOME

Archive: /softtmp/p6880880_112000_AIX64-5L.zip

extracting: /oracle/app/oracle/product/11.2.0/db/OPatch/version.txt

replace /oracle/app/oracle/product/11.2.0/db/OPatch/opatch.bat? [y]es, [n]o, [A]ll, [N]one, [r]ename: A

inflating: /oracle/app/oracle/product/11.2.0/db/OPatch/opatch.bat

inflating: /oracle/app/oracle/product/11.2.0/db/OPatch/opatchprereqs/opatch/opatch_prereq.xml

inflating: /oracle/app/oracle/product/11.2.0/db/OPatch/opatchprereqs/opatch/rulemap.xml

《《《《。。。。。。。。篇幅原因，有省略。。。。。。。。》》》》

inflating: /oracle/app/oracle/product/11.2.0/db/OPatch/oplan/jlib/bundle.jar

inflating: /oracle/app/oracle/product/11.2.0/db/OPatch/oplan/README.txt

inflating: /oracle/app/oracle/product/11.2.0/db/OPatch/opatchdiag

ZHLHRDB1:oracle:/oracle>opatch version

OPatch Version: 11.2.0.3.12 ====》grid用户的OPatch软件升级成功

OPatch succeeded.

root用户分别在节点1和节点2生成ocm.rsp文件

The OPatch utility will prompt for your OCM (Oracle Configuration Manager) response file when it is run. You should enter a complete path of OCM response file if you already have created this in your environment. OCM response file is required and is not optional.

ZHLHRDB1:root:/softtmp>$ORACLE_HOME/OPatch/ocm/bin/emocmrsp -no_banner -output /softtmp/ocm_11gR2_psu5_lhr.rsp

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

The OCM configuration response file (/softtmp/ocm_11gR2_psu5_lhr.rsp) was successfully created.

total 2425576

drwxr-xr-x 2 root system 256 May 05 15:31 lost+found

-rw-r--r-- 1 root system 621 May 17 10:10 ocm_11gR2_psu5_lhr.rsp

-rwxrwxrwx 1 oracle dba 1187252238 May 17 09:44 p14727347_112030_AIX64-5L.zip

-rwxrwxrwx 1 root system 54636538 May 16 22:13 p6880880_112000_AIX64-5L.zip

开始升级GI PSU软件包

说明：一定要按照顺序一个节点一个节点的打，会同时升级当前节点的GRID和DB SOFTWARE。

解压PSU包

首先升级节点一：

ZHLHRDB1:root:/softtmp>mkdir psu5

total 2425576

drwxr-xr-x 2 root system 256 May 05 15:31 lost+found

-rw-r--r-- 1 root system 621 May 17 10:10 ocm_11gR2_psu5_lhr.rsp

-rwxrwxrwx 1 oracle dba 1187252238 May 17 09:44 p14727347_112030_AIX64-5L.zip

-rwxrwxrwx 1 root system 54636538 May 16 22:13 p6880880_112000_AIX64-5L.zip

drwxr-xr-x 2 root system 256 May 17 10:17 psu5

ZHLHRDB1:root:/softtmp>unzip p14727347_112030_AIX64-5L.zip -d ./psu5/

Archive: p14727347_112030_AIX64-5L.zip

creating: ./psu5/14727310/

creating: ./psu5/14727310/14727310/

creating: ./psu5/14727310/14727310/etc/

creating: ./psu5/14727310/14727310/etc/xml/

inflating: ./psu5/14727310/14727310/etc/xml/ShiphomeDirectoryStructure.xml

《《《《。。。。。。。。篇幅原因，有省略。。。。。。。。》》》》

inflating: ./psu5/15876003/files/srvm/lib/ins_srvm.mk

creating: ./psu5/15876003/files/inventory/

creating: ./psu5/15876003/files/inventory/Scripts/

creating: ./psu5/15876003/files/inventory/Scripts/ext/

creating: ./psu5/15876003/files/inventory/Scripts/ext/jlib/

inflating: ./psu5/15876003/files/inventory/Scripts/ext/jlib/cvu.jar

inflating: ./psu5/README.html

extracting: ./psu5/README.txt

inflating: ./psu5/bundle.xml

total 2425576

drwxr-xr-x 2 root system 256 May 05 15:31 lost+found

-rw-r--r-- 1 root system 621 May 17 10:10 ocm_11gR2_psu5_lhr.rsp

-rwxrwxrwx 1 oracle dba 1187252238 May 17 09:44 p14727347_112030_AIX64-5L.zip

-rwxrwxrwx 1 root system 54636538 May 16 22:13 p6880880_112000_AIX64-5L.zip

drwxr-xr-x 4 root system 256 May 17 10:18 psu5

ZHLHRDB1:root:/softtmp>chmod -R 777 psu5

ZHLHRDB1:root:/softtmp>l ./psu5

total 128

drwxrwxrwx 7 root system 256 Jan 12 2013 14727310

drwxrwxrwx 5 root system 256 Jan 12 2013 15876003

-rwxrwxrwx 1 root system 54667 Jan 14 2013 README.html

-rwxrwxrwx 1 root system 21 Jan 12 2013 README.txt

-rwxrwxrwx 1 root system 450 Jan 12 2013 bundle.xml

测试兼容性

Before beginning patch application, check the consistency of inventory information for GI home and each database home to be patched. Run the following command as respective Oracle home owner to check the consistency.

分别对oracle和grid用户进行检查：

$ORACLE_HOME/OPatch/opatch lsinventory -detail -oh $ORACLE_HOME

$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /softtmp/psu5 -oh $ORACLE_HOME

其实在安装过程中也会自动校验是否有冲突，若有冲突也会退出安装的。

ZHLHRDB1:oracle:/oracle>$ORACLE_HOME/OPatch/opatch lsinventory -detail -oh $ORACLE_HOME

Oracle Interim Patch Installer version 11.2.0.3.12

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

Oracle Home : /oracle/app/oracle/product/11.2.0/db

Central Inventory : /oracle/app/oraInventory

from : /oracle/app/oracle/product/11.2.0/db/oraInst.loc

OPatch version : 11.2.0.3.12

OUI version : 11.2.0.3.0

Log file location : /oracle/app/oracle/product/11.2.0/db/cfgtoollogs/opatch/opatch2016-05-17_10-35-15AM_1.log

Lsinventory Output file location : /oracle/app/oracle/product/11.2.0/db/cfgtoollogs/opatch/lsinv/lsinventory2016-05-17_10-35-15AM.txt

--------------------------------------------------------------------------------

Local Machine Information::

Hostname: ZHLHRDB1

ARU platform id: 212

ARU platform description:: IBM_AIX

Installed Top-level Products (1):

Oracle Database 11g 11.2.0.3.0

后续精彩内容已被小麦苗无情隐藏，请输入验证码解锁本站所有文章！

验证码：

请先关注本站微信公众号，然后回复“验证码”，获取验证码。在微信里搜索“DB宝”或者“www_xmmup_com”或者微信扫描右侧二维码都可以关注本站微信公众号。