Oracle 19c rac 安装补丁 Patch 32226239

6.冲突检测：

The following commands check for conflicts in both the 12.1 GI home and the 12.1 DB homes.

#GRID_HOME/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/32226239 -analyze

#GRID_HOME/OPatch/opatchauto rollback <UNZIPPED_PATCH_LOCATION>/32226239 -analyze

7.opatchauto 2节点分别打补丁：

Oracle RAC, where the GI Home and the Database Homes are not shared and ACFS file system is not configured.

As root user, execute the following command on each node of the cluster:

# <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/32226239

[root@19crac1 ~]# /oracle/grid/OPatch/opatchauto apply /oracle/32226239/
OPatchauto session is initiated at Thu Feb 25 13:59:24 2021
System initialization log file is /oracle/grid/cfgtoollogs/opatchautodb/systemconfig2021-02-25_01-59-27PM.log.
Session log file is /oracle/grid/cfgtoollogs/opatchauto/opatchauto2021-02-25_01-59-37PM.log
The id for this session is H3CQ
Executing OPatch prereq operations to verify patch applicability on home /oracle/grid
Patch applicability verified successfully on home /oracle/grid
Executing patch validation checks on home /oracle/grid
Patch validation checks successfully completed on home /oracle/grid
Performing prepatch operations on CRS - bringing down CRS service on home /oracle/grid
Prepatch operation log file location: /oracle/gridbase/crsdata/19crac1/crsconfig/crs_prepatch_apply_inplace_19crac1_2021-02-25_02-00-20PM.log
CRS service brought down successfully on home /oracle/grid
Start applying binary patch on home /oracle/grid
   
Binary patch applied successfully on home /oracle/grid
Performing postpatch operations on CRS - starting CRS service on home /oracle/grid
Postpatch operation log file location: /oracle/gridbase/crsdata/19crac1/crsconfig/crs_postpatch_apply_inplace_19crac1_2021-02-25_02-14-41PM.log
CRS service started successfully on home /oracle/grid
OPatchAuto successful.
--------------------------------Summary--------------------------------
Patching is completed successfully. Please find the summary as follows:
Host:19crac1
CRS Home:/oracle/grid
Version:19.0.0.0.0
Summary:
==Following patches were SUCCESSFULLY applied:
Patch: /oracle/32226239/29340594
Log: /oracle/grid/cfgtoollogs/opatchauto/core/opatch/opatch2021-02-25_14-03-16PM_1.log
Patch: /oracle/32226239/32218454
Log: /oracle/grid/cfgtoollogs/opatchauto/core/opatch/opatch2021-02-25_14-03-16PM_1.log
Patch: /oracle/32226239/32218663
Log: /oracle/grid/cfgtoollogs/opatchauto/core/opatch/opatch2021-02-25_14-03-16PM_1.log
Patch: /oracle/32226239/32222571
Log: /oracle/grid/cfgtoollogs/opatchauto/core/opatch/opatch2021-02-25_14-03-16PM_1.log
Patch: /oracle/32226239/32240590
Log: /oracle/grid/cfgtoollogs/opatchauto/core/opatch/opatch2021-02-25_14-03-16PM_1.log
OPatchauto session completed at Thu Feb 25 14:18:07 2021
Time taken to complete the session 18 minutes, 43 seconds

8.检查补丁情况/oracle/grid/OPatch/opatch lsinv 版本号也从19.3升级到19.10 [grid@19crac1 log]$ sqlplus -v SQL*Plus: Release 19.0.0.0.0 - ProductionVersion 19.10.0.0.0 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++

众所周知，oracle19.3版本的集群环境中，在opatch升级时，因为oraInventory/ContentsXML目录下的oui-patch的权限问题，在打DBpatch时除了第一节点之外，均会有如下报错：

手动打补丁报错信息：

自动打补丁报错信息：

Patch: /tmp/grid_path/30116789/30122149  

当然如果oui-patch.xml文件在执行chmod+w 解决完权限问题之后，opatchautoresume可以自动执行，但是如果你是手动打补丁，权限问题解决之后并不能解决问题，并且不能回退，如下图所示：

上述问题可以通过如下方法可以避免和解决：

a)、在开始打除了第一节点之外的DBpatch之前，就执行chmod+w

b)、安装时加上applyPSU参数

c)、还原备份文件

d)、如果此时你也没有备份，那能做的只有删除再添加节点了。