Database Crashes with OSD-04008, O/S-Error: (OS 33)
(Doc ID 1415635.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 11.1.0.6 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Generic Windows
Symptoms
Database crashes subsequent to following errors in the alert log:
KCF: write/open error block=0x392c8d online=1
file=32 D:\ORACLE\ORADATA...
error=27072 txt: '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.'
Errors in file d:\oracle\diag\rdbms...dbw4_692.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01114: IO error writing block to file 32 (block # 3746957)
ORA-01110: data file 32: 'D:\ORACLE\ORADATA....
ORA-27072: File 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.
DBW4 (ospid: 692): terminating the instance due to error 1242
Thu Jan 26 15:28:30 2012
Error occured while spawning process m000; error = 1242
Instance terminated by DBW4, pid = 692
file=32 D:\ORACLE\ORADATA...
error=27072 txt: '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.'
Errors in file d:\oracle\diag\rdbms...dbw4_692.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01114: IO error writing block to file 32 (block # 3746957)
ORA-01110: data file 32: 'D:\ORACLE\ORADATA....
ORA-27072: File 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.
DBW4 (ospid: 692): terminating the instance due to error 1242
Thu Jan 26 15:28:30 2012
Error occured while spawning process m000; error = 1242
Instance terminated by DBW4, pid = 692
Restarting the Database resolves the issue temorarily. This error eventually reoccurs and Database crashes again.
- DB Verify has been run on the affected datafile but reported no corruption.
- Could not identify the process holding the lock on the file using:
tlist, command line interface (downloadable from the windows resource kit).
Process Explorer, from Microsoft previous sysinternals. - No anti-virus software was running.
- Windows Check Disk did not detect any bad sectors on the disk.
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 |