Top 5 ASM instance startup Issues in RAC Environment
(Doc ID 2247920.1)
Last updated on JANUARY 01, 2020
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 11.2 to 12.1]
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 document is to provide summary of top ASM instance startup issues and the possible solutions in a RAC environment.
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: ASM instance not getting started from specific nodes on a RAC cluster|
|Issue #2: ASM coming up, but going down due to side effect of node eviction, ocr diskgroup dismount etc|
|Issue #3: Unable to start ASM if OS CPUs # > 64|
|Issue #4: oraagent indicates "ORA-01017: invalid username/password; logon denied" while starting up asm|
|Issue #5: ASM instance not getting auto-mount diskgroups on reboot, but manual startup works fine|