ASM Unable To Get Logical Block Size For ASM Spfile
(Doc ID 2158451.1)
Last updated on APRIL 12, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
When starting ASM instance, it cannot read asm spfile from diskgroup.
Error message in ASM alert log is:
gpnp profile has the correct spfile and asm understands which is the spfile but cannot read it.
Parameters specified in spfile are not in effect. Also ASM instances runs without spfile
ASM diskgroups have sector size 512 bytes.
Recreating spfile on other diskgroups does not help either. However creating spfile on non ASM location works and spfile is recognized.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |