TOP 5 RDBMS Instance Crash as a Result of ASM
(Doc ID 2248030.1)
Last updated on FEBRUARY 03, 2020
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
The purpose of this note is to provide a summary of the Top 5 RDBMS instance as a result of ASM issues
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
|Issue #1:Instance Crash After Random Errors ORA-15080: Synchronous I/O Operation To A Disk Failed|
|Issue #2:Instance Crash ORA-27041, ORA-15080, ORA-63999, ORA-01114, ORA-15081|
|Issue #3:Database fails to recover with error ORA-29709 and terminates by RBAL process|
|Issue #4:Instance terminated by ASMB, pid "PMON failed to acquire latch "|
|Issue #5:Databases Fail With ORA-03115 And ORA-15064 When ASM Disk Or Exadata Griddisk Goes Offline|