CRS-2883: Resource 'ora.asm' failed during Clusterware stack start

Symptoms
========

root@oraprod02:~# /u01/app/12.1.0.2/grid/crs/install/rootcrs.pl -postpatch
Using configuration parameter file: /u01/app/12.1.0.2/grid/crs/install/crsconfig_params
2017/11/05 15:57:38 CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector.

2017/11/05 15:58:08 CLSRSC-4003: Successfully patched Oracle Trace File Analyzer (TFA) Collector.

2017/11/05 15:58:13 CLSRSC-329: Replacing Clusterware entries in file '/etc/inittab'

CRS-4123: Oracle High Availability Services has been started.
CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Starting Oracle High Availability Services-managed resources
CRS-2672: Attempting to start 'ora.evmd' on 'oraprod02'
CRS-2672: Attempting to start 'ora.mdnsd' on 'oraprod02'
CRS-2676: Start of 'ora.mdnsd' on 'oraprod02' succeeded
CRS-2676: Start of 'ora.evmd' on 'oraprod02' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'oraprod02'
CRS-2676: Start of 'ora.gpnpd' on 'oraprod02' succeeded
CRS-2672: Attempting to start 'ora.gipcd' on 'oraprod02'
CRS-2676: Start of 'ora.gipcd' on 'oraprod02' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'oraprod02'
CRS-2676: Start of 'ora.cssdmonitor' on 'oraprod02' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'oraprod02'
CRS-2672: Attempting to start 'ora.diskmon' on 'oraprod02'
CRS-2676: Start of 'ora.diskmon' on 'oraprod02' succeeded
CRS-2676: Start of 'ora.cssd' on 'oraprod02' succeeded
CRS-2672: Attempting to start 'ora.ctssd' on 'oraprod02'
CRS-2676: Start of 'ora.ctssd' on 'oraprod02' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'oraprod02'
CRS-5017: The resource action "ora.asm start" encountered the following error:
ORA-03113: end-of-file on communication channel
Process ID: 0
Session ID: 0 Serial number: 0
. For details refer to "(:CLSN00107:)" in "/u01/app/oracle/diag/crs/oraprod02/crs/trace/ohasd_oraagent_oracle.trc".
CRS-2883: Resource 'ora.asm' failed during Clusterware stack start.
CRS-4406: Oracle High Availability Services synchronous start failed.
CRS-4000: Command Start failed, or completed with errors.
2017/11/05 15:59:55 CLSRSC-117: Failed to start Oracle Clusterware stack

Died at /u01/app/12.1.0.2/grid/crs/install/crspatch.pm line 941.



Cause
=====

This issue could be due to file permission issue in some of the binary files in the Grid home.

You can check and compare the same from both nodes under $GRID_HOME/bin

Please check for any files with the wrong permission.

Also check the following files found under from both nodes.

/u01/app/12.1.0.2/grid/crs/utl/<hostname>/

* crsconfig_fileperms
* crsconfig_dirs


Solution
======

As root user:

# <GRID_HOME>/bin/crsctl stop crs -f

# cd <GRID_HOME>/crs/install

# ./rootcrs.pl -unlock

# ./rootcrs.pl -patch

Comments

Post a Comment

Popular posts from this blog

Fatal agent error: Target Interaction Manager failed at Startup

Symptoms ========  $ /AGENT_INST/bin/emctl start agent Oracle Enterprise Manager Cloud Control 12c Release 3 Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved. Starting agent ......................................................................... failed. Fatal agent error: Target Interaction Manager failed at Startup Fatal agent error: Target Interaction Manager failed at Startup Fatal agent error: Target Interaction Manager failed at Startup EMAgent is Thrashing. Exiting watchdog $/AGENT_INST/sysman/log/emagent.nohup reports following error 2013-11-01 17:29:38,596 [1:main] WARN - Missing filename for log handler 'opsscfg' Agent is going down due to an OutOfMemoryError $/AGENT_INST/sysman/log/gcagent.log reports following error 2013-11-01 17:29:19,204 [1:3305B9] INFO - Invoking STARTUP_P1 (1) on Target Interaction Manager 2013-11-01 17:29:23,255 [1:main] FATAL - Fatal error: Target Interaction Manager failed at Startup java.lang.OutOfMemoryError: Java heap sp
Read more

[INS-40718] Single Client Access Name (SCAN): could not be resolved. ( LDOMS & Zones)

Cause The name you provided as the SCAN could not be resolved using TCP/IP host name lookup. Action-Provide name to use for the SCAN for which the domain can be resolved Global Zone : ============= # svccfg svc:> select name-service/switch svc:/system/name-service/switch> setprop config/host = astring: "files dns" svc:/system/name-service/switch> select system/name-service/switch:default svc:/system/name-service/switch:default> refresh svc:/system/name-service/switch:default> validate svc:/system/name-service/switch:default> exit # svcadm refresh name-service/switch # svcadm restart /system/name-service-cache; then, I can resolve host using telnet/ping.
Read more