Database Fails To Start After GI Upgrade To 12.2 With ORA-15040

(Doc ID 2247077.1)

Last updated on OCTOBER 15, 2017

Applies to:

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

Symptoms

Cluster was upgraded from 12.1 to 12.2.

Afterwards, this database won't start and fails saying diskgroup is incomplete, but the diskgroup is complete and mounted .

 

 


2017-03-15T14:19:06.264175-05:00
NOTE: client oidstl2d2:oidstl2d:danlrlb950-RL no longer has group 2 (DATA) mounted
NOTE: client oidstl2d2:oidstl2d:danlrlb950-RL no longer has group 2 (DATA) mounted
NOTE: client oidstl2d2:oidstl2d:danlrlb950-RL no longer has group 8 (FLASH_SMALL) mounted
2017-03-15T14:19:11.163543-05:00
NOTE: ASM client oidstl2d2:oidstl2d:danlrlb950-RL disconnected unexpectedly.
NOTE: check client alert log.
NOTE: Trace records dumped in trace file /opt/oracrs/gridbase/diag/asm/+asm/+ASM2/trace/+ASM2_ufg_42188_oidstl2d2_oidstl2d.trc
NOTE: cleaned up ASM client oidstl2d2:oidstl2d:danlrlb950-RL connection state (reg:3385155183)
2017-03-15T14:19:14.029953-05:00
NOTE: detected orphaned client id 0x10006.
NOTE: detected orphaned client id 0x10000.
2017-03-15T14:24:14.151872-05:00
NOTE: timeout (300s) expired for orphan ownerid 0x10000 for client oidstl2d2:oidstl2d:danlrlb950-RL; 301s elapsed
WARNING: giving up on client id 0x10000 [oidstl2d2:oidstl2d:danlrlb950-RL] which has not reconnected for 301 seconds (originally from ASM inst +ASM2, reg:3385155183) [timeout]
NOTE: removing stale ownerid 0x10000 for client oidstl2d2:oidstl2d:danlrlb950-RL (reg:3385155183)
NOTE: released resources held for client id 0x10000 (reg:3385155183)

File_name :: alert_+ASM2.log

 

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