Opatchauto fails with OPATCHAUTO-72141: Grid patching cannot be performed in rolling mode on single node cluster
(Doc ID 2336186.1)
Last updated on MARCH 07, 2022
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Opatch fails in single node GI as below.
Screen output :
root@xyz:~# export PATH=$PATH:/opt/oragrid/12102/OPatch
root@xyz:/opt/oragrid/stage/patches# opatchauto apply 26635815
OPatchauto session is initiated at Thu Nov 2 22:13:45 2017
System initialization log file is $GRID_HOME/cfgtoollogs/opatchautodb/systemconfig2017-11-02_10-13-51PM.log.
Session log file is $GRID_HOME/cfgtoollogs/opatchauto/opatchauto2017-11-02_10-13-58PM.log
The id for this session is 2G22
OPATCHAUTO-72141: Grid patching cannot be performed in rolling mode.
OPATCHAUTO-72141: Grid is installed only on a single node.
OPATCHAUTO-72141: Execute opatchauto in non-rolling mode.
OPatchauto session completed at Thu Nov 2 22:14:04 2017
Time taken to complete the session 0 minute, 19 seconds
opatchauto failed with error code 42
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