logical block size mismatch ASM spfile on ASM diskgroup is not in use
(Doc ID 2197212.1)
Last updated on MARCH 23, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 and laterInformation in this document applies to any platform.
Symptoms
ASM instance is not reading the spfile created on ASM disks.
.
SQL> startup
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file '+GRID/test/spfiletest.ora'
ORA-17503: ksfdopn:10 Failed to open file +GRID/test/spfiletest.ora
.
.
asmcmd ls +TEST/test/asmparameterfile/registry.253.916429303
ASMCMD-8001: diskgroup 'TEST' does not exist or is not mounted
Thu Jun 02 09:50:16 2016
ALTER SYSTEM RESET asm_diskgroups SCOPE=SPFILE SID='+ASM1';
Thu Jun 02 09:52:01 2016
ALTER SYSTEM SET
asm_diskgroups='DATA','FRA' SCOPE=BOTH
freeing rdom 0
Thu Jun 02 11:28:11 2016
Instance shutdown complete
Thu Jun 02 13:20:44 2016
NOTE: No asm libraries found in the system
ERROR: -6(Size mismatch 1048576 4194304)
ERROR: -6(Size mismatch 1048576 4194304)
ERROR: -6(Size mismatch 1048576 4194304)
ERROR: Unable to get logical block size for spfile
'+GRID/test/asmparameterfile/registry.253.913471741'.
* instance_number obtained from CSS = 1, checking for the existence of node
0...
* node 0 does not exist. instance_number = 1
.
.
ERROR: Unable to get logical block size for spfile
'+GRID/test/asmparameterfile/registry.253.917791837'.
MEMORY_TARGET defaulting to 2852126720.
*
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |