[bhsieh]

Instance terminating due to error 221

Hello all,

I am receving the following error periodically:

ORA-00206: error in writing (block 3, # blocks 1) of controlfile
ORA-00202: controlfile: 'E:\NEW\CONTROL02.CTL'
ORA-27072: skgdisp: 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.

ORA-00221: error on write to controlfile
ORA-00206: error in writing (block 3, # blocks 1) of controlfile
ORA-00202: controlfile: 'E:\NEW\CONTROL02.CTL'
ORA-27072: skgdisp: 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.

CKPT: terminating instance due to error 221
Instance terminated by CKPT, pid = 3504


This problem seems to happen just before the database files are backed up by Veritas Netbackup. However, the Oracle agent is configured for this database, and this problem happens sporadically. In addition, the database is bounced prior to the Veritas backup.

I have disabled Norton Antivirus from scanning the control files of the database during our nightly scans. How can I tell what is locking the control file??

Thanks!

[Hings]

Dear bhsieh,

I guess you can resolve this problem By ..

Recreating the CONTROLFILE followed by recovery.

Hope this will help you out.

Thanks

Hings,

==========

Still learning...

[yumi_rama]

Is the control file in a network drive, if it is move it to local disk and try again.

[clio_usa]

To see which process is using which files, install a small Windows program called - handle. Here is the URL - http://www.sysinternals.com/ntw2k/freeware/handle.shtml

For control file locking you have to check the NetBackup setup. It shouldn't lock the control files, unless you are doing something wronf during the backup. BTW, are you using RMAN & NetBackup?



Hope that helps,

clio_usa - OCP - DBA