Top Issues : Encountered while adding ASM disk to ASM Diskgroup
(Doc ID 2247475.1)
Last updated on JANUARY 24, 2020
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 188.8.131.52 [Release 10.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 Database Cloud Exadata 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 issues that are encountered during adding ASM disk to the ASM Diskgroup
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 Unable To Add New Disks With Dissimilar Size To 184.108.40.206 ASM Diskgroups (Normal or High Redundancy) Due To ORA-15410|
|Issue #2 ORA-15038: Disk '' Mismatch on 'Sector Size' with Target Disk Group   Using 4K SECTOR_SIZE Disks|
|Issue #3 ORA-00600: internal error code, arguments: [kfgscRevalidate_1], , , |