Oracle terminated due to control file locked (Legacy KB ID CNC TS17012 )

Document ID : KB000052125
Last Modified Date : 14/02/2018
Show Technical Document Details

This is also a common problem when using backup software. The backup utility locks the datafile, controlfile or logfile. When Oracle attempts to write to the file, the lock prevents it and the database crashes. Backup software should be configured so it does not lock open files. In this case, contact the third party vendor for information on how to not lock open files.

Related Issues/Questions:
Oracle terminated due to control file locked
System crashes
Oracle instance stops
From the $ORACLE_HOME\admin\bdump\{$ORACLE_SID}\alert_{$ORACLE_SID}.log file
Usually: $ORACLE_HOME\admin\bdump\EHEALTH\alert_EHEALTH.log


Example message:


Errors in $ORACLE_HOME\admin\bdump\ile c:\oracle\oracle.9.2\ehealth\ehealth_ckpt_1372.trc:


ORA-00221: error on write to controlfile
ORA-00206: error in writing (block 3, # blocks 1) of controlfile
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.

Problem Environment:
eHealth 5.5 and later

(Legacy KB ID CNC TS17012 )