Unable To Add ASM Disk That Previously Failed Because It Was Not Cluster-Wide Visible: ORA-15030
(Doc ID 1498420.1)
Last updated on SEPTEMBER 16, 2021
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 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
Information in this document applies to any platform.
It was not know at the time the first attempt to add the disk that it was not visible on some of the clustered nodes.
Therefore the 1st attempt failed:
Despite of the above error/failure, the ASM disk header of the disk was updated as a member of the ASM disk group by the nodes where the disk was visible.
However, the ASM metadata still is unaware that the disk is fully part of the ASM disk group, nor data has been moved to the new disk. Hence, the disk is truly not part of the ASM disk group.
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