mopatch oracle_Oracle 19c RAC打补丁过程避坑指南

最新推荐文章于 2024-03-26 18:19:29 发布

猴小贼

最新推荐文章于 2024-03-26 18:19:29 发布

阅读量947

点赞数

CC 4.0 BY-SA版权

文章标签： mopatch oracle

本文链接：https://blog.youkuaiyun.com/weixin_32203421/article/details/112833802

本文详细记录了Oracle 19c Real Application Clusters (RAC) 打补丁过程中遇到的常见问题及其解决方案，包括权限不足、内部错误、OPatchauto失败等，并提供了错误排查和解决步骤，旨在帮助读者避免类似问题，顺利进行补丁安装。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

3. 先打gi补丁【节点1打完，再打节点2】，使用opatchauto。

打gi要用gi_home的opatchauto，打oracle用oracle_home的opatchauto ,切记都是在root下面执行命令,这时用的是全路径，配置Path切换容易出错。

4. 检查gi是否成功

OPatch succeeded.

5. 打db补丁【节点1打完，再打节点2】，使用opatchauto。

6. 检查db是否成功

OPatch succeeded.

7. 打OJVM补丁【节点1打完，再打节点2】

8. 回退方法

#db回退/u01/app/ oracle/product/ 19.3.0/db_1/OPatch/opatchauto rollback/tmp/grid_path/ 30116789-oh /u01/app/ oracle/product/ 19.3.0/db_1

9. 小结

先打节点1，或2都行，没有强制要求先打节点1，习惯而已。补丁安装过程中可能会遇到各种权限问题及其它问题，后面针对遇到的问题都做了下记录，让后面的人少踩坑。

二、遇到的一些错误

错误No.1

After fixing the cause of failure Run opatchauto resume

]OPATCHAUTO-68061: The orchestration engine failed.OPATCHAUTO-68061: The orchestration engine failed withreturncode 1OPATCHAUTO -68061: Checkthe logformore details.OPatchAuto failed.

OPatchauto sessioncompleted atMon Mar 917: 45: 312020Timetaken tocompletethe session1minute, 16seconds

opatchauto failedwitherrorcode 42

问题描述:

DB补丁安装过程中报出的权限不足，具体原因不明，没有深入去分析,19c打补丁过程中会遇到各种权限问题。

解决办法:

#resume是接着上次失败的地方继续安装的意思。[ root@xydb8node1 ~] # /u01/app/oracle/product/19.3.0/db_1/OPatch/opatchauto resume

错误No.2

2020-03-1011: 18: 19.081[OHASD( 147218)]CRS -6015: OracleClusterware has experienced an internal error. Details at(:CLSGEN00100:) { 0: 0: 2} in/u01/app/grid/diag/crs/xydb8node2/crs/ trace/ohasd.trc.2020-03-1011: 18: 19.106[OHASD( 147218)]CRS -8505: OracleClusterware OHASD process withoperating systemprocess ID147218encountered internal errorCRS -06015

trace日志：/u01/app/grid/diag/crs/xydb8node2/crs/ trace/ohasd.trc截取部份错误日志，如下：

2020-03-1011: 18: 19.057:CRSSHARED: 4034262784: [ INFO] [F-ALGO]{ 0: 0: 2} getIpcPath returning(ADDRESS=(PROTOCOL=IPC)( KEY=OHASD_UI_SOCKET))2020-03-1011: 18: 19.058:GIPCXCPT: 4038465280: gipcInternalConnectSync: failedsyncrequest, addr 0x7f9c9405c720[ 000000000000b814] { gipcAddress : name'clsc://(ADDRESS=(PROTOCOL=ipc)(KEY=SYSTEM.evm.acceptor.auth)(GIPCID=00000000-00000000-0))', objFlags 0x0, addrFlags 0x4}, ret gipcretConnectionRefused ( 29)2020-03-1011: 18: 19.058:GIPCXCPT: 4038465280: gipcConnectSyncF [EvmConConnect : evmgipcio.c : 235]: EXCEPTION[ ret gipcretConnectionRefused ( 29) ] failedsyncconnectendp 0x7f9c9405b2a0[ 000000000000b80d] { gipcEndpoint : localAddr 'clsc://(ADDRESS=(PROTOCOL=ipc)(KEY=)(GIPCID=00000000-00000000-0))', remoteAddr 'clsc://(ADDRESS=(PROTOCOL=ipc)(KEY=SYSTEM.evm.acceptor.auth)(GIPCID=00000000-00000000-0))', numPend 0, numReady 0, numDone 0, numDead 1, numTransfer 0, objFlags 0x0, pidPeer 0, readyRef (nil), ready 1, wobj 0x7f9c9405e350, sendp 0x7f9c9405e100status13flags 0xa108871a, flags -20x0, usrFlags 0x30020}, addr 0x7f9c9405c720[ 000000000000b814] { gipcAddress : name'clsc://(ADDRESS=(PROTOCOL=ipc)(KEY=SYSTEM.evm.acceptor.auth)(GIPCID=00000000-00000000-0))', objFlags 0x0, addrFlags 0x4}, flags 0x80000002020-03-1011: 18: 19.058:UiServer: 4034262784: [ INFO] { 0: 0: 2} GIPC address: clsc://(ADDRESS=(PROTOCOL=IPC)( KEY=OHASD_UI_SOCKET))2020-03-1011: 18: 19.058: GIPC: 4034262784: sgipcnDSBindHelper: file/ var/tmp/.oracle/sOHASD_UI_SOCKET_lock islockedbyPID 1471622020-03-1011: 18: 19.058:GIPCXCPT: 4034262784: gipcmodNetworkProcessBind: failedtobind endp 0x7f9c8c000950[ 000000000000b819] { gipcEndpoint : localAddr 'clsc://(ADDRESS=(PROTOCOL=ipc)(KEY=OHASD_UI_SOCKET)(GIPCID=00000000-00000000-0))', remoteAddr '', numPend 0, numReady 0, numDone 0, numDead 0, numTransfer 0, objFlags 0x0, pidPeer 0, rea