ASM instance crashed and not starting
(Doc ID 2907514.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 19.12.0.0.0 and laterSUSE \ UnitedLinux x86-64
Symptoms
ASM instance crashed with below errors on one node
NOTE: ASMB process exiting, either shutdown is in progress or foreground connected to ASMB was killed.
NOTE: ASMB clearing idle groups before exit
2022-10-31T11:03:21.444103+01:00
PMON (ospid: 17005): terminating the instance due to ORA error 495
2022-10-31T11:03:21.444299+01:00
Cause - 'Instance is being terminated due to fatal process death (pid: 6, ospid: 17048, GEN0)'
2022-10-31T11:03:22.446464+01:00
Instance terminated by PMON, pid = 17005
NOTE: ASMB clearing idle groups before exit
2022-10-31T11:03:21.444103+01:00
PMON (ospid: 17005): terminating the instance due to ORA error 495
2022-10-31T11:03:21.444299+01:00
Cause - 'Instance is being terminated due to fatal process death (pid: 6, ospid: 17048, GEN0)'
2022-10-31T11:03:22.446464+01:00
Instance terminated by PMON, pid = 17005
No errors found in Gen0 and ASMB trace files
DB instances running/started using flex ASM
crsd oraagent is crashing with below error
CRS-8503 [__lll_unlock_elision()+48] [Signal/Exception: 11] [Instruction Addr: 0x7f6824fcb790] [Memory Addr: (nil)] [] [] [] [] [] [] [] []
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 |
| Cause |
| |
| Solution |
| References |