Opatchauto:fails with error CLSRSC-493: failed to initiate rolling patch on the current node because there is only one active HUB node
(Doc ID 2308972.1)
Last updated on JULY 10, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
Symptoms
'opatchauto apply' Fails Due to CLSRSC-493 and opatchauto error code 42 while it attempts to run "rootcrs.pl -prepatch":
......
Command failed: /u01/app/12.2.0/grid/perl/bin/perl -I/u01/app/12.2.0/grid/perl/lib -I/u01/app/12.2.0/grid/OPatch/auto/dbtmp/bootstrap_node1/patchwork/crs/install /u01/app/12.2.0/grid/OPatch/auto/dbtmp/bootstrap_node1/patchwork/crs/install/rootcrs.pl -prepatch
Command failure output:
Using configuration parameter file: /u01/app/12.2.0/grid/OPatch/auto/dbtmp/bootstrap_node1/patchwork/crs/install/crsconfig_params
The log of current session can be found at:
/oracle_base/crsdata/node1/crsconfig/crspatch_node1_2017-09-14_10-52-01AM.log
2017/09/14 10:52:05 CLSRSC-493: failed to initiate rolling patch on the current node because there is only one active HUB node
After fixing the cause of failure Run opatchauto resume with session id "D5QJ"
]
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 Thu Sep 14 10:52:05 2017
Time taken to complete the session 3 minutes, 2 seconds
opatchauto failed with error code 42
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 |
Cause |
Solution |
References |