Top Issues : Encountered while Configuring ASM disks on Linux with ASMLIB
(Doc ID 2245259.1)
Last updated on JANUARY 01, 2020
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Oracle Database Cloud Schema 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
Oracle Database Backup Service - Version N/A and later
The purpose of this document is to provide a summary of the top issues that may be encountered while configuring ASM disks on Linux with ASMLIB.
This note applies to Grid Infrastructure for both Clustered and Standalone ASM 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: How To Verify If A New Candidate ASM Disk Is Cluster Wide Visible ORA-15075 / ORA-15080|
|Issue #2: All the asmlib disks appear in ASM's v$asm_disk view, however their HEADER_STATUS=UNKNOWN|
|Issue #3: ASMLib Devices Not Discovered with Diskstring as 'ORCL:*'|
|Issue #4: root.sh fails during GI installation on the first node with ORA-15303 in ASM alert.log|