思庄oracle技术分享-OPATCHAUTO-68061 编制引擎失败

最新推荐文章于 2023-07-31 09:14:48 发布
最新推荐文章于 2023-07-31 09:14:48 发布
阅读量1.2k 收藏 1
点赞数
分类专栏： oracle数据库 文章标签： oracle 数据库
原文链接：http://bbs.cqsztech.com/forum.php?mod=viewthread&tid=29847&extra=page%3D1
版权

数据库：19.3
系统：CentOS 7.9
数据库升级过程中遭遇OPATCHAUTO-68061报错，如下：
[root@hisdb2 OPatch]# ./opatchauto resume

OPatchauto session is initiated at Sat Mar 19 23:29:20 2022
Session log file is /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/opatchauto2022-03-19_11-29-20PM.log
Resuming existing session with id 4D22

Start applying binary patch on home /u01/app/oracle/product/19.3.0/db
Binary patch applied successfully on home /u01/app/oracle/product/19.3.0/db

Performing postpatch operation on home /u01/app/oracle/product/19.3.0/db
Postpatch operation completed successfully on home /u01/app/oracle/product/19.3.0/db

Start applying binary patch on home /u01/app/19.3.0/grid
Failed while applying binary patches on home /u01/app/19.3.0/grid

Execution of [OPatchAutoBinaryAction] patch action failed, check log for more details. Failures:
Patch Target : hisdb2->/u01/app/19.3.0/grid Type[crs]
Details: [
---------------------------Patching Failed---------------------------------
Command execution failed during patching in home: /u01/app/19.3.0/grid, host: hisdb2.
Command failed: /u01/app/19.3.0/grid/OPatch/opatchauto apply /soft/31750108 -oh /u01/app/19.3.0/grid -target_type cluster -binary -invPtrLoc /u01/app/19.3.0/grid/oraInst.loc -jre /u01/app/19.3.0/grid/OPatch/jre -persistresult /u01/app/19.3.0/grid/opatchautocfg/db/sessioninfo/sessionresult_hisdb2_crs_1.ser -analyzedresult /u01/app/19.3.0/grid/opatchautocfg/db/sessioninfo/sessionresult_analyze_hisdb2_crs_1.ser
Command failure output:
==Following patches FAILED in apply:

Patch: /soft/31750108/31771877
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-19_23-34-30PM_1.log
Reason: Failed during Patching: oracle.opatch.opatchsdk.OPatchException: ApplySession failed in system modification phase… ‘ApplySession::apply failed: java.io.IOException: oracle.sysman.oui.patch.PatchException: java.io.FileNotFoundException: /u01/app/oraInventory/ContentsXML/oui-patch.xml (Permission denied)’

After fixing the cause of failure Run opatchauto resume
]
OPATCHAUTO-68061: The orchestration engine failed.
OPATCHAUTO-68061: The orchestration engine failed with return code 1
OPATCHAUTO-68061: Check the log for more details.
OPatchAuto failed.

OPatchauto session completed at Sat Mar 19 23:39:15 2022
Time taken to complete the session 9 minutes, 56 seconds

opatchauto failed with error code 42

故障解决solution：
观察节点1与节点2 /oracle/oraInventory/ContentsXML/oui-patch.xml权限差异，并将节点二修改成与节点1一致。
[root@hisdb1 OPatch]# ll /u01/app/oraInventory/ContentsXML/oui-patch.xml
-rw-rw---- 1 grid oinstall 174 Mar 19 22:49 /u01/app/oraInventory/ContentsXML/oui-patch.xml
[root@hisdb2 OPatch]# ll /u01/app/oraInventory/ContentsXML/oui-patch.xml
-rw-r–r-- 1 oracle oinstall 174 Mar 19 23:34 /u01/app/oraInventory/ContentsXML/oui-patch.xml
[root@hisdb2 OPatch]# chown -R grid:oinstall /u01/app/oraInventory/ContentsXML/oui-patch.xml
[root@hisdb2 OPatch]# chmod g+w /u01/app/oraInventory/ContentsXML/oui-patch.xml
[root@hisdb2 OPatch]# ll /u01/app/oraInventory/ContentsXML/
total 20
-rw-rw---- 1 grid oinstall 300 Mar 19 23:34 comps.xml
-rw-rw---- 1 grid oinstall 555 Mar 14 23:14 inventory.xml
-rw-rw---- 1 grid oinstall 292 Mar 19 23:34 libs.xml
-rw-rw-r-- 1 grid oinstall 174 Mar 19 23:34 oui-patch.xml
-rw-r–r-- 1 grid oinstall 174 Mar 19 23:34 oui-patch.xml.back

./opatchauto resume 继续执行
[root@hisdb2 OPatch]# ./opatchauto resume

OPatchauto session is initiated at Sun Mar 20 08:45:24 2022
Session log file is /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/opatchauto2022-03-20_08-45-24AM.log
Resuming existing session with id 4D22

Start applying binary patch on home /u01/app/19.3.0/grid
Failed while applying binary patches on home /u01/app/19.3.0/grid

Execution of [OPatchAutoBinaryAction] patch action failed, check log for more details. Failures:
Patch Target : hisdb2->/u01/app/19.3.0/grid Type[crs]
Details: [
---------------------------Patching Failed---------------------------------
Command execution failed during patching in home: /u01/app/19.3.0/grid, host: hisdb2.
Command failed: /u01/app/19.3.0/grid/OPatch/opatchauto apply /soft/31750108 -oh /u01/app/19.3.0/grid -target_type cluster -binary -invPtrLoc /u01/app/19.3.0/grid/oraInst.loc -jre /u01/app/19.3.0/grid/OPatch/jre -persistresult /u01/app/19.3.0/grid/opatchautocfg/db/sessioninfo/sessionresult_hisdb2_crs_1.ser -analyzedresult /u01/app/19.3.0/grid/opatchautocfg/db/sessioninfo/sessionresult_analyze_hisdb2_crs_1.ser
Command failure output:
==Following patches FAILED in apply:

Patch: /soft/31750108/31771877
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-20_08-45-52AM_1.log
Reason: Failed during Analysis: CheckNApplyReport Failed, [ Prerequisite Status: FAILED, Prerequisite output:
The details are:
Unable to create patchObject
Possible causes are:
ORACLE_HOME/inventory/oneoffs/31771877 is corrupted. PatchObject constructor: Input file “/u01/app/19.3.0/grid/inventory/oneoffs/31771877/etc/config/actions” or “/u01/app/19.3.0/grid/inventory/oneoffs/31771877/etc/config/inventory” does not exist.
]
After fixing the cause of failure Run opatchauto resume
]
OPATCHAUTO-68061: The orchestration engine failed.
OPATCHAUTO-68061: The orchestration engine failed with return code 1
OPATCHAUTO-68061: Check the log for more details.
OPatchAuto failed.

OPatchauto session completed at Sun Mar 20 08:45:57 2022
Time taken to complete the session 0 minute, 33 seconds

opatchauto failed with error code 42

依然报错
查看补丁信息：(也出现报错)
[grid@hisdb2:/home/grid]$ opatch lsinventory
Oracle Interim Patch Installer version 12.2.0.1.28
Copyright © 2022, Oracle Corporation. All rights reserved.

Oracle Home : /u01/app/19.3.0/grid
Central Inventory : /u01/app/oraInventory
from : /u01/app/19.3.0/grid/oraInst.loc
OPatch version : 12.2.0.1.28
OUI version : 12.2.0.7.0
Log file location : /u01/app/19.3.0/grid/cfgtoollogs/opatch/opatch2022-03-20_08-47-30AM_1.log

Lsinventory Output file location : /u01/app/19.3.0/grid/cfgtoollogs/opatch/lsinv/lsinventory2022-03-20_08-47-30AM.txt

Inventory load failed… OPatch cannot load inventory for the given Oracle Home.

LsInventorySession failed: Unable to create patchObject
Possible causes are:
ORACLE_HOME/inventory/oneoffs/31771877 is corrupted. PatchObject constructor: Input file “/u01/app/19.3.0/grid/inventory/oneoffs/31771877/etc/config/actions” or “/u01/app/19.3.0/grid/inventory/oneoffs/31771877/etc/config/inventory” does not exist.

OPatch failed with error code 73

故障解决，根据MOS2286025.1 solution：
从节点1拷贝
[grid@hisdb1:/u01/app/19.3.0/grid/inventory/oneoffs]$ scp -r 31771877/ hisdb2:/u01/app/19.3.0/grid/inventory/oneoffs/
inventory.xml 100% 319KB 46.9MB/s 00:00
actions.xml 100% 2331KB 70.4MB/s 00:00
在节点2再次resume
[root@hisdb2 OPatch]# ./opatchauto resume

OPatchauto session is initiated at Sun Mar 20 08:51:40 2022
Session log file is /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/opatchauto2022-03-20_08-51-41AM.log
Resuming existing session with id 4D22

Start applying binary patch on home /u01/app/19.3.0/grid
Binary patch applied successfully on home /u01/app/19.3.0/grid

Checking shared status of home…

Performing postpatch operations on CRS - starting CRS service on home /u01/app/19.3.0/grid
Postpatch operation log file location: /u01/app/grid/crsdata/hisdb2/crsconfig/crs_postpatch_apply_inplace_hisdb2_2022-03-20_08-55-32AM.log
CRS service started successfully on home /u01/app/19.3.0/grid

Preparing home /u01/app/oracle/product/19.3.0/db after database service restarted
No step execution required…

Trying to apply SQL patch on home /u01/app/oracle/product/19.3.0/db
SQL patch applied successfully on home /u01/app/oracle/product/19.3.0/db

OPatchAuto successful.
--------------------------------Summary--------------------------------
Patching is completed successfully. Please find the summary as follows:

Host:hisdb2
RAC Home:/u01/app/oracle/product/19.3.0/db
Version:19.0.0.0.0
Summary:

==Following patches were SKIPPED:

Patch: /soft/31750108/31773437
Reason: This patch is not applicable to this specified target type - “rac_database”

Patch: /soft/31750108/31780966
Reason: This patch is not applicable to this specified target type - “rac_database”

==Following patches were SUCCESSFULLY applied:

Patch: /soft/31750108/31771877
Log: /u01/app/oracle/product/19.3.0/db/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-19_23-29-38PM_1.log

Patch: /soft/31750108/31772784
Log: /u01/app/oracle/product/19.3.0/db/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-19_23-29-38PM_1.log

Host:hisdb2
CRS Home:/u01/app/19.3.0/grid
Version:19.0.0.0.0
Summary:

==Following patches were SKIPPED:

Patch: /soft/31750108/31771877
Reason: This patch is not applicable to this specified target type - “cluster”

==Following patches were SUCCESSFULLY applied:

Patch: /soft/31750108/31772784
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-20_08-52-08AM_1.log

Patch: /soft/31750108/31773437
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-20_08-52-08AM_1.log

Patch: /soft/31750108/31780966
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-20_08-52-08AM_1.log

OPatchauto session completed at Sun Mar 20 09:07:08 2022
Time taken to complete the session 15 minutes, 28 seconds
执行成功

duanweifang
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Oracle 19c rac OPatch 19.5 补丁升级报错 The orchestration engine failed with return code 1
jisen_huang的专栏
03-31 720
apply日志 [root@rac19c2 u01]# $GI_ORACLE_HOME/OPatch/opatchauto apply $UNZIPPED_PATCH_LOCATION Start applying binary patch on home /u01/app/19.0.0/grid Failed while applying binary patches on home /u0...
19c 打补丁遇到节点2 OPATCHAUTO-68061 报错
董董的^数据空间
09-12 3381
文章目录遇到了两次OPATCHAUTO-68061 报错第一次 OPATCHAUTO-68061 的报错信息解决办法第二次 OPATCHAUTO-68061 的报错信息解决办法 遇到了两次OPATCHAUTO-68061 报错 按照正常的打补丁流程： 1. 分别在node1、node2上，升级GI OPatch 2. 分别在node1、node2上，升级Oracle OPatch 3. 分别在node1、node2上，给GI 打补丁 4. 分别在node1、node2上，给Oracle打补丁 结果就在成功
oracle 19c打补丁遭遇OPATCHAUTO-72043&OPATCHAUTO-68061
www_xue_xi的博客
07-31 1035
最近，在AIX上的新装oracle 19C数据库基础版本，使用opatchauto打PSU补丁集35037840时遇到了OPATCHAUTO-72043报错，无法正常应用GI补丁。关于autopatch GI打补丁报错OPATCHAUTO-72043，清除掉OPatch目录，重新解压最新的opatch工具并赋权后，重新使用opatchauto打补丁能够执行。关于autopatch GI打补丁报错OPATCHAUTO-68061，oracle 官网文档12202307.9中提到可能是已知问题。
Oracle 19c 问题解决
jnrjian的博客
05-27 2441
使用plsql Developer连接时，发现报ora-28040No matching authentication protocol select username, account_status, default_tablespace, created, password_versions from dba_users; password_versions表示当前用户是口令的认证方式。 [oracle@test ~]$ oerr ora 28040 28040, 000...
【无标题】Oracle 12c安装补丁失败，会话日志报错Prerequisite check “CheckApplicable“ failed
lambto的博客
03-31 580
详细日志报错 Copy Action:Destination File “***” is not writeable。会话日志报错 Prerequisite check “CheckApplicable” failed。该情况是因为上一次安装补丁失败造成的权限不对称的原因。
Oracle面试问题-技术篇.doc
12-21
Oracle面试问题-技术篇 Oracle面试问题-技术篇是Oracle数据库管理系统的一些常见问题和解答，这些问题涵盖了数据库备份、恢复、配置、存储结构等多个方面。下面是对这些问题的详细解释和知识点总结： 1. 冷备份和...
dm8-oracle-jdbc16-wrapper.jar
11-18
dm8-oracle-jdbc16-wrapper.jar
oracle-xe-11.2.0-1.0.x86_64.rpm.zip
07-02
oracle-xe-11.2.0-1.0.x86_64.rpm
2- Oracle 12C NON-CDB数据库安装.docx
04-17
在安装 Oracle 12C NON-CDB 数据库之前，需要安装一些必需的软件包，包括 x11、gnome、oracle-rdbms-server-12cR1-preinstall 和 tigervnc-server。这些软件包的安装可以使用 yum 命令来实现。 oracle-rdbms-server-...
甲骨论技术论坛-Oracle视频教程（46集）
07-23
教程名称：甲骨论技术论坛-Oracle视频教程（46集）课程目录：【】甲骨论技术论坛-Oracle视频教程0~2【】甲骨论技术论坛-Oracle视频教程3~6【】甲骨论技术论坛-Oracle视频教程7~9【】甲骨论技术论坛-Oracle视频教程10...
p6880880_112000_Linux-x86-64.zip(11.2.0.3.21)
04-28
p6880880_112000_Linux-x86-64.zip(11.2.0.3.21) 最新Opath补丁安装软件，注意是64位的操作系统。请配合最新补丁进行安装p29255947_112040_Linux-x86-64.zip、p29141056_112040_Linux-x86-64.zip
记录Oracle rac 19C（19.15）补丁升级（OPatch 33803476）操作过程
狗剩儿的记忆博客
07-20 1757
提示以下是本篇文章正文内容，下面案例可供参考。
Oracle 19c RAC 遇到的几个问题
JiekeXu的博客
03-23 2160
作者 | JiekeXu来源 |公众号 JiekeXu DBA之路（ID: JiekeXu_IT）大家好，我是 JiekeXu,很高兴又和大家见面了,今天和大家一起来看看 Oracle 19c RAC 遇到的几个问题，欢迎点击上方蓝字关注我，标星或置顶，更多干货第一时间到达！Oracle19c 作为长期支持的大版本，是很多公司和个人选择的主流数据库版本，很多公司新上线的系...
打dbpatch中“Prerequisite check "CheckApplicable" failed. ”问题解决方法
mwyu316的博客
03-22 3064
测试小姐姐说，测试环境和生产环境补丁号有不同，如图：发现是dbpatch只在oracle用户下打了，没在grid用户下打，于是补上了。在打补丁的过程中报了错：---------------------------Patching Failed---------------------------------Command execution failed during patching in ho...
Oracle报错object存在,ORACLE 19C RAC FOR RHEL7 打补丁报错OPatchException: Unable to create patchObject...
weixin_42416119的博客
04-12 523
6月15号，在做oracle 19c for rhel7.6安装及打补丁时，遭遇了Unable to create patchObject和oui-patch.xml(权限不够)报错。这里记录一下问题分析处理过程，备忘！集群环境的基本信息：1、两节点的rac2、操作系统版本rhel7.63、数据库版本19.3.04、应用补丁包p30899722_190000_Linux-x86-64.zip问题场...
aq.yy.com/app/yysec/index.html,gpc-20201123
热门推荐
weixin_33245735的博客
06-27 6万+
0000040987-20-000050.txt : 202011230000040987-20-000050.hdr.sgml : 2020112320201123163353ACCESSION NUMBER:0000040987-20-000050CONFORMED SUBMISSION TYPE:8-KPUBLIC DOCUMENT COUNT:16CONFORMED PERIOD OF R...
oracle升级补丁报错,Oracle 19c rac OPatch 19.5 补丁升级报错 The orchestration engine failed with return code 1...
weixin_39611510的博客
04-07 207
apply日志[root@rac19c2 u01]# $GI_ORACLE_HOME/OPatch/opatchauto apply $UNZIPPED_PATCH_LOCATIONStart applying binary patch on home /u01/app/19.0.0/gridFailed while applying binary patches on home /u01/app...
oracle报错3150,Oracle RAC 实例 升级后无法启动 ORA-01565,ORA-17503,ORA-12547 解决方法
weixin_28889007的博客
04-05 860
Oracle 18c RAC 环境，节点2数据库实例启动失败，报错如下：https://www.cndba.cn/cndba/dave/article/3150[oracle@www.cndba.cn dbs]$ sqlplus / as sysdbaSQL*Plus: Release 18.0.0.0.0 - Production on Sun Nov 18 03:16:39 2018Versi...
Oracle 19c RAC打补丁过程避坑指南
Enmotech的博客
03-13 4331
墨天轮原文链接：https://www.modb.pro/db/22393 导读：记录19.3 rac 打补丁过程中遇到的一些问题19.3升19.5、19.5升19.6。 新装的19.3 rac 需要安装补丁，目前最新的RU是19.6，由于最新的可能不稳定，选择了次新的19.5，打第一套比较顺利，后面的几套都出现些大大小小的问题 ，记录一下。 19.3存在一个比较严重的cr...
Oracle 12C In-Memory Column Store特性
最新发布
03-04
Oracle 12C In-Memory Column Store是一项关键性能增强技术，对于需要处理大量数据分析的场景，能够带来显著的查询响应速度提升。理解并有效利用这一特性，是数据库管理员优化数据库性能的重要手段。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值