READING CONTROLFILE ERRORS AT WINDOWS STARTUP ON ASM (Doc ID 556187.1)

Last updated on JUNE 21, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.1.0.6 [Release 10.1 to 11.1]
z*OBSOLETE: Microsoft Windows 2000
z*OBSOLETE: Microsoft Windows Server 2003
Microsoft Windows (32-bit)
Microsoft Windows 2000Microsoft Windows Server 2003Microsoft Windows (32-bit)

Symptoms

After windows startup is completed, one or more databases instances having files (controlfiles, datafiles) on ASM diskgroups fails to start with errors accessing controlfiles:


ORA-00204: error in reading (block 1, # blocks 1) of controlfile
ORA-00202: controlfile: '+DG1/controfile1'
ORA-17507: I/O request size 8192 is not a multiple of logical block size
Controlfile identified with block size 0
ORA-205 signalled during: ALTER DATABASE MOUNT...


Errors are found in alert.log in database instance and database instance stays in mount mode. Next attempt to startup the database instance manually succeeds.

In the oradim.log, it is found that +ASM service is started after the database services.
For example:


Sun Feb 17 17:05:02 2008
D:\oracle\product\10.1.0\db_1\bin\oradim.exe -startup -sid +asm -usrpwd * -log oradim.log -nocheck 0

Sun Feb 17 17:04:50 2008
D:\oracle\product\10.1.0\db_1\bin\oradim.exe -startup -sid ORCL1 -usrpwd * -log oradim.log -nocheck 0

Sun Feb 17 17:05:09 2008
ORA-00205: error in identifying control file

Sun Feb 17 17:04:50 2008
D:\oracle\product\10.1.0\db_1\bin\oradim.exe -startup -sid ORCL2 -usrpwd * -log oradim.log -nocheck 0

Sun Feb 17 17:05:09 2008
ORA-00205: error in identifying control file

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms