opatchauto fails if asm_diskstring is not set in 12c (Doc ID 2253553.1)

Last updated on APRIL 22, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.2.0.1 [Release 12.1 to 12.2]
Information in this document applies to any platform.

Symptoms

The opatchauto command fails during postpatch with error code 2.

Applying patch(es) to "/u01/app/12.1.0.2/grid" ...
Patch "/u01/stage/oracle12c/psupatch/24917825/21436941" applied to "/u01/app/12.1.0.2/grid" with warning.
Patch "/u01/stage/oracle12c/psupatch/24917825/24732082" applied to "/u01/app/12.1.0.2/grid" with warning.
Patch "/u01/stage/oracle12c/psupatch/24917825/24828633" applied to "/u01/app/12.1.0.2/grid" with warning.
Patch "/u01/stage/oracle12c/psupatch/24917825/24828643" applied to "/u01/app/12.1.0.2/grid" with warning.

Performing postpatch operations on CRS Home... Failed
Command "/u01/app/12.1.0.2/grid/perl/bin/perl -I/u01/app/12.1.0.2/grid/perl/lib -I/u01/app/12.1.0.2/grid/OPatch/opatchautotemp_pplconcdedbph04/patchwork/crs/install /u01/app/12.1.0.2/grid/OPatch/opatchautotemp_pplconcdedbph04/patchwork/crs/install/rootcrs.pl -postpatch" execution failed:
Died at /u01/app/12.1.0.2/grid/OPatch/opatchautotemp_pplconcdedbph04/patchwork/crs/install/crspatch.pm line 932.


For more details, please refer to the log file "/u01/app/12.1.0.2/grid/cfgtoollogs/opatchauto/24917825/opatch_gi_2017-03-17_00-45-41_deploy.debug.log".

Apply Summary:

opatchauto ran into some warnings during patch installation (Please see log file for details):
GI Home: /u01/app/12.1.0.2/grid: 21436941,24732082,24828633,24828643
Command failure exception

opatchauto failed with error code 2.

 

The opatch_gi_2017-03-17_00-45-41_deploy.debug.log shows that the cssdmonitor fails to start

 Clusterware startup failed to start resource ora.cssdmonitor and couldn't startup the clusterware .

> CRS-2676: Start of 'ora.diskmon' on 'pplconcdedbph04' succeeded
> CRS-2883: Resource 'ora.cssdmonitor' failed during Clusterware stack start. <<<<<<<<<<<
> CRS-4406: Oracle High Availability Services synchronous start failed.
> CRS-4000: Command Start failed, or completed with errors.
>End Command output
2017-03-17 00:52:44: The return value of blocking start of CRS: 1
2017-03-17 00:52:44: Failed to start the Oracle CRS stack
2017-03-17 00:52:44: Executing cmd: /u01/app/12.1.0.2/grid/bin/clsecho -p has -f clsrsc -m 117
2017-03-17 00:52:44: Executing cmd: /u01/app/12.1.0.2/grid/bin/clsecho -p has -f clsrsc -m 117
2017-03-17 00:52:44: Command output:
> CLSRSC-117: Failed to start Oracle Clusterware stack
>End Command output
2017-03-17 00:52:44: CLSRSC-117: Failed to start Oracle Clusterware stack
....

2017-03-17_00-52-46 :

--------------After fixing the cause of failure you have two options shown below:
Run 'opatchauto resume'
or
Manually run the commands listed below

 

Changes

Applying the GI PSU.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms