Top ASM Instance Crash Issues
(Doc ID 2247412.1)
Last updated on DECEMBER 24, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Purpose
The purpose of this note is to provide a summary of the Top 5 issues that may caus ASM Instance Crash
Scope
Details
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
| Purpose |
| Scope |
| Details |
| Issue #1: ASM Instance Terminated by PMON Due to Error 488 |
| Issue #2: ASM Instance Terminated with ORA-00445 and ORA-29743 |
| Issue #3: ASM Instances may crash after reporting ORA-04031 Errors |
| Issue #4: ASM and DB Crash if RAC Instance Is Up For > 248 Days by LMHB with ORA-29770 on Solaris |
| References |