rootupgrade.sh fails on node1 as HAIP was not starting from old home but starting from new home (Doc ID 2063676.1)

Last updated on AUGUST 20, 2016

Applies to:

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

Symptoms

Upgrading Grid Infrastructure from 11.2.0.3 to 11.2.0.4, rootupgrade.sh fails on node1: 

# ./rootupgrade.sh
....
CRS-4000: Command Start failed, or completed with errors.
Failed to start Oracle Grid Infrastructure stack
Failed to start ASM at /db/crs/oracle/11.2.0.4/crs/install/crsconfig_lib.pm line 1339.


<NEW_GI_HOME>/cfgtoollogs/crsconfig/rootcrs_<node>.log

2015-09-25 11:59:50: Executing cmd: /db/crs/oracle/11.2.0.4/bin/crsctl start resource ora.asm -init
2015-09-25 12:01:47: Command output:
> CRS-2672: Attempting to start 'ora.drivers.acfs' on 'dbs2'
> CRS-2676: Start of 'ora.drivers.acfs' on 'dbs2' succeeded
> CRS-2672: Attempting to start 'ora.asm' on 'dbs2'
> 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 "/db/crs/oracle/11.2.0.4/log/dbs2/agent/ohasd/oraagent_grid/oraagent_grid.log".
> CRS-2674: Start of 'ora.asm' on 'dbs2' failed
> CRS-2679: Attempting to clean 'ora.asm' on 'dbs2'
> CRS-2681: Clean of 'ora.asm' on 'dbs2' succeeded
> CRS-2673: Attempting to stop 'ora.drivers.acfs' on 'dbs2'
> CRS-2677: Stop of 'ora.drivers.acfs' on 'dbs2' succeeded
> CRS-4000: Command Start failed, or completed with errors.
>End Command output
2015-09-25 12:01:47: Executing cmd: /db/crs/oracle/11.2.0.4/bin/crsctl check resource ora.asm -init
2015-09-25 12:01:47: Executing cmd: /db/crs/oracle/11.2.0.4/bin/crsctl status resource ora.asm -init


ASM alert

Cluster communication is configured to use the following interface(s) for this instance
169.254.72.18
169.254.160.175
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
Fri Sep 25 12:00:01 2015
....
lmon registered with NM - instance number 1 (internal mem no 0)
Fri Sep 25 12:01:22 2015
No connectivity to other instances in the cluster during startup. Hence, LMON is terminating the instance. Please check the LMON trace file for details. Also, please check the network logs of this instance along with clusterwide network health for problems and then re-start this instance.
LMON (ospid: 12386536): terminating the instance
Fri Sep 25 12:01:22 2015
ORA-1092 : opitsk aborting process


ASM alert while the node was able to join the cluster

Cluster communication is configured to use the following interface(s) for this instance
10.82.120.47
192.168.0.52
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
Fri Sep 25 10:58:47 2015
PMON started with pid=2, OS id=13303912

 

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