My Oracle Support Banner

ASM FAILS TO START ON NON-FIRST NODE DUIRNG GI UPGRADE FROM 12.2 TO 19C. (Doc ID 2630422.1)

Last updated on JANUARY 27, 2020

Applies to:

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

Symptoms

During the GI form 12.2 to 19.5 version, ASM instance is able to start only on one node. Only first node is upgraded, the second node is till in 12.2 version and ASM not starting during upgrade on 2nd node.

oifcfg getif
bond0  xxx.xxx.xxx.0  global  public
priv0  xxx.xx.xx.0  global  cluster_interconnect,asm
priv1  xxx.xx.xx.xxx  global  cluster_interconnect,asm
priv0  169.xxx.0.0  global  cluster_interconnect


ASM2 crashed with following error
-------------------------------------------------
Warning: Oraping detected connectivity issues.
An eviction is expected due environment issues
OS ping to instance: 1 has failed.
Please see LMON and oraping trace files for details.


2019-12-09T10:14:56.831830+01:00
Instance Critical Process (pid: 15, ospid: 599294, LMON) died unexpectedly
PMON (ospid: 597916): terminating the instance due to error 481
2019-12-09T10:14:56.854207+01:00
System state dump requested by (instance=2, osid=597916 (PMON)), summary=[abnormal instance termination].
System State dumped to trace file <ORACLE_BASE>/diag/asm/+asm/+ASM2/trace/+ASM2_diag_599215_20191209101456.trc
======================

ohasd_orarootagent_root.trc
=====================
35019 2019-12-11 23:30:02.427 : USRTHRD:2664605440: [     INFO] {0:5:3} Failed to check 169.xxx.30.109 on priv0
35020 2019-12-11 23:30:02.427 : USRTHRD:2664605440: [     INFO] {0:5:3}
(null) category: 0, operation: , loc: , OS error: 0, other
..
35132 routedata 172.xxx.xxx.128 / 0.0.0.0 / xxx.xxx.xxx.128 / priv1 / priv1
35133 checkipinSubnet xxx.xxx.xxx.128, 169.xxx.0.0
35134 routedata dest not in subnet
35135 upgrade 1
35136 add routedata 169.xxx/16 / xxx.17.xxx.1 / xxx.xxx.0.0 / priv0 / priv0
35137 IP route failed 169.xxx/16 / xxx.xxx.0.0 / xxx.17.xxx.1 / priv0
35138 ation: routeadd, loc: system, OS error: 11, other: failed to execute route add, ret 256===========>

 

Changes

 Upgrading GI from 12.2 to 19c

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
Changes
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.