ASM Instance Terminated Itself with ORA-00445 and ORA-29743
Last updated on DECEMBER 12, 2017
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 11.2 to 12.1]
Information in this document applies to any platform.
alert_+ASM<instance number>.log shows
LMD0 (ospid: <>) waits for event 'ges remote message' for 173 secs.
GES: System Load is HIGH.
GES: Current load is 80.00 and high load threshold is 20.00
ORA-00445: background process "m001" did not start after 120 seconds
Incident details in: <>/diag/asm/+asm/+ASM1/incident/incdir_<>/+ASM1_mmon_<>_i<>.trc
Dumping diagnostic data in directory=[cdmp_<>], requested by (instance=<>, osid=<> (MMON)), summary=[incident=<>].
IPC Send timeout detected. Receiver ospid <> [oracle@<> (LMD0)]
This instance is not in good health as some of its
receivers are not making progress.
Hence this instance is gracefully terminating itself <<<<< HERE<<<and
will not participate in the current IMR reconfiguration.
Errors in file <>/diag/asm/+asm/+ASM1/trace/+ASM1_lmon_<>.trc:
ORA-29743: exiting from instance membership recovery protocol because this instance is not in good health
System state dump requested by (instance=<>, osid=<> (LMON)), summary=[abnormal instance termination]. <<<<<<<<< HERE <<<<<<<<<<<<<<
System State dumped to trace file <>/diag/asm/+asm/+ASM1/trace/+ASM1_diag_<>_<DATETIME>.trc
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms