ORA-00221 and OSD-04008 as Database is Unable to write to control files
Last updated on SEPTEMBER 09, 2016
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Microsoft Windows x64 (64-bit)
***Checked for relevance on 09-Sep-2016***
OSD-04008 implies OS specific issues. The first thing that need to be investigated is the existence of one of the following:
1- Virus checker running on that machine. Virus checker locks files as it scan them. If this is the case, configure the antivirus to do not scan the databases files.
2- Operating system backup software that backs up the database folders. Some customers uses backup software from remote servers to backup all their servers at night. If yes, can you disable it or reconfigure it to exclude Oracle database folders.
Three different database instances run on the same machine hanged around the same time. The following errors are reported in the alert.log file:
One instance reported
ORA-01186: file 22 failed verification tests
ORA-01122: database file 22 failed verification check
ORA-01110: data file 22: 'D:\ORADATA\BUSDATDV\UNDO01_01.DBF'
ORA-01208: data file is an old version - not accessing current version
Another instance reported:
ORA-00221: error on write to controlfile
ORA-00206: error in writing (block 3, # blocks 1) of controlfile
ORA-00202: controlfile: 'C:\ORACLE\ORADATA\MAPDATDV\CONTROL02.CTL'
ORA-27072: skgfdisp: I/O error
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.
Please note that the reported filename and type might be different. One instance reported an undo file, other reported inability to access control but the common error is
No changes on the database environment
No Operating system patches
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms