My Oracle Support Banner

opatchauto -analyze fails with "OPATCHAUTO-72030: Cannot execute in rolling mode, as CRS home is shared" for GI Home & "OPATCHAUTO-72051: OpatchAuto cannot proceed when DB is running on other nodes from the shared home being patched" for RAC Home (Doc ID 3045246.1)

Last updated on SEPTEMBER 06, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

opatchauto analyze fails on GI Home with the below Error-

[root@rachost2 install]# $ORACLE_HOME/OPatch/opatchauto apply /u01/install/36233126 -analyze

OPatchauto session is initiated at Fri Jul 19 14:13:18 2024

System initialization log file is /u01/app/product/19.0.0/grid_home1/cfgtoollogs/opatchautodb/systemconfig2024-07-19_02-13-42PM.log.

Session log file is /u01/app/product/19.0.0/grid_home1/cfgtoollogs/opatchauto/opatchauto2024-07-19_02-14-04PM.log
The id for this session is VARG
Shared home /u01/app/product/19.0.0/grid_home1 can only be patched in nonrolling mode.

OPATCHAUTO-72030: Execution mode invalid.
OPATCHAUTO-72030: Cannot execute in rolling mode, as CRS home is shared.
OPATCHAUTO-72030: Execute in non-rolling mode.
OPatchAuto failed.

OPatchauto session completed at Fri Jul 19 14:14:22 2024
Time taken to complete the session 0 minute, 41 seconds

opatchauto failed with error code 42

opatchauto -analyze may also fail on RAC Home with the below error-

[root@rachost2 install]# $ORACLE_HOME/OPatch/opatchauto apply /u01/install/36233126 -analyze

OPatchauto session is initiated at Tue Aug 13 10:55:16 2024

System initialization log file is /u01/app/product/19.0.0/grid_home1/cfgtoollogs/opatchautodb/systemconfig2024-08-13_10-55-39AM.log.

Session log file is /u01/app/product/19.0.0/grid_home1/cfgtoollogs/opatchauto/opatchauto2024-08-13_10-56-02AM.log
The id for this session is JYMM
OPATCHAUTO-72051: DB running on other nodes from shared home.
OPATCHAUTO-72051: OpatchAuto cannot proceed when DB is running on other nodes from the shared home being patched.
OPATCHAUTO-72051: Execute stop db on other shared home.
OPatchAuto failed.

OPatchauto session completed at Tue Aug 13 10:56:18 2024
Time taken to complete the session 0 minute, 40 seconds

opatchauto failed with error code 42
[root@rachost2 install]#



Changes

 ~grid/.ssh/known_hosts was missing on the Cluster Nodes.
Steps from MOS Note - Opatchauto failing due to SSH connectivity failure (Doc ID 2946767.1) were followed

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.