My Oracle Support Banner

ORA-15158: rolling upgrade prevented by One or more modules not ready for RM (Doc ID 2618093.1)

Last updated on JANUARY 23, 2020

Applies to:

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

Symptoms

The following errors have occurred while applying the OCT GI PSU.

Opatch auto command output

$ sudo ./opatchauto apply $GI_HOME/patch/30116802 -oh /orab/app/oracle/1220/gridinf
Enter password for local user oracle:

OPatchauto session is initiated at Thu Dec 5 23:57:54 2019

System initialization log file is $GI_HOME/cfgtoollogs/opatchautodb/systemconfig2019-12-05_11-57-58PM.log.

Session log file is $GI_HOME/cfgtoollogs/opatchauto/opatchauto2019-12-05_11-58-48PM.log
The id for this session is NYHU

Executing OPatch prereq operations to verify patch applicability on home $GI_HOME
Patch applicability verified successfully on home /orab/app/oracle/1220/gridinf

Bringing down CRS service on home $GI_HOME
Prepatch operation log file location:$ORALCE_BASE/crsdata/tpdclpdbspkoc1a/crsconfig/crspatch_tpdclpdbspkoc1a_2019-12-05_10-59-08PM.log
Failed to bring down CRS service on home $GI_HOME

Execution of [GIShutDownAction] patch action failed, check log for more details. Failures:
Patch Target : tpdclpdbspkoc1a->$GI_HOME Type[crs]
Details: [
---------------------------Patching Failed---------------------------------
Command execution failed during patching in home:$GI_HOME, host: tpdclpdbspkoc1a.
Command failed: $GI_HOME/perl/bin/perl -I$GI_HOME/perl/lib -I $GI_HOME/OPatch/auto/dbtmp/bootstrap_<nodename>/patchwork/crs/install $GI_HOMEf/OPatch/auto/dbtmp/bootstrap_<nodename>/patchwork/crs/install/rootcrs.pl -prepatch
Command failure output:
Using configuration parameter file: $GI_HOME/OPatch/auto/dbtmp/bootstrap_<nodename>/patchwork/crs/install/crsconfig_params
The log of current session can be found at:
$ORACLE_BASE/crsdata/tpdclpdbspkoc1a/crsconfig/crspatch_<nodename>_2019-12-05_10-59-08PM.log
Oracle Clusterware active version on the cluster is [12.2.0.1.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [170607330].
ORA-15158: rolling upgrade prevented by One or more modules not ready for RM
CRS-4698: Error code 2 in retrieving the patch levelCRS-1154: There was an error setting Oracle ASM to rolling patch mode.
CRS-4000: Command Start failed, or completed with errors.
2019/12/05 23:00:09 CLSRSC-430: Failed to start rolling patch mode

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 Fri Dec 6 00:00:10 2019
Time taken to complete the session 2 minutes, 16 seconds

opatchauto failed with error code 42

crspatch_<nodename>_2019-12-05_10-18-32PM.log:

2019-12-05 22:19:06: Executing $GI_HOME/bin/crsctl query crs activeversion -f
2019-12-05 22:19:06: Executing cmd: $GI_HOME/bin/crsctl query crs activeversion -f
2019-12-05 22:19:06: Command output:
> Oracle Clusterware active version on the cluster is [12.2.0.1.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [170607330].
>End Command output
2019-12-05 22:19:06: Setting the GI stack for rolling patch application ...
2019-12-05 22:19:06: Setting the cluster in rolling patch mode ...
2019-12-05 22:19:06: Executing cmd: $GI_HOME/bin/crsctl start rollingpatch
2019-12-05 22:19:30: Command output:
> ORA-15158: rolling upgrade prevented by One or more modules not ready for RM
> CRS-4698: Error code 2 in retrieving the patch levelCRS-1154: There was an error setting Oracle ASM to rolling patch mode.
> CRS-4000: Command Start failed, or completed with errors.
>End Command output
2019-12-05 22:19:30: Executing cmd: $GI_HOME/bin/clsecho -p has -f clsrsc -m 430
2019-12-05 22:19:31: Command output:
> CLSRSC-430: Failed to start rolling patch mode
>End Command output
2019-12-05 22:19:31: CLSRSC-430: Failed to start rolling patch mode
2019-12-05 22:19:31: ###### Begin DIE Stack Trace ######
2019-12-05 22:19:31: Package File Line Calling
2019-12-05 22:19:31: --------------- -------------------- ---- ----------
2019-12-05 22:19:31: 1: main rootcrs.pl 287 crsutils::dietrap
2019-12-05 22:19:31: 2: crspatch crspatch.pm 1101 main::__ANON__
2019-12-05 22:19:31: 3: crspatch crspatch.pm 997 crspatch::performPrePatch
2019-12-05 22:19:31: 4: crspatch crspatch.pm 239 crspatch::crsPrePatch
2019-12-05 22:19:31: 5: main rootcrs.pl 296 crspatch::new
2019-12-05 22:19:31: ####### End DIE Stack Trace #######

2019-12-05 22:19:31: ROOTCRS_PREPATCH checkpoint has failed

 

 

 

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


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