On Sunday I did an upgrade from Oracle7 to Oracle9; uninstalled Oracle7; rebooted; installed 184.108.40.206; installed...
patch 220.127.116.11; created database skeleton; imported user data from Oracle 7; and exported into Oracle 18.104.22.168. From what I view the database is not in archive log mode. Monday the database switches one log at 12:18 and one checkpoint happens at 14:21. Tuesday the database switches one log at 8:51 and one checkpoint at 10:55. At 15:22 the database crashes with ORA-00206, ORA-00202, ORA-27072, OSD-04008 and O/S Error (OS 33). The process cannot access the file because another process has locked a portion of the file. The file is the third control file.
On Wednesday, this exact same thing happens.
Do you know of any quirks in Windows that may cause this due to database settings or the Windows layer?
We do not have anti-virus software loaded on the server due to problems; the backups were excluding the database folder; and there are not any other pieces of software running that we know of to be trying to read this file. We do have TrackIT, but I was told this software reads the system-level info.
Thank you for your help.
Related Q&A from Brian Peasland
Oracle expert Brian Peasland answers one reader's question about common pitfalls when connecting Oracle to outside programs.continue reading
One reader asks expert Brian Peasland a question about datafile sizes with the Oracle RMAN duplicate 10g command.continue reading
Managing parent table-child table relations in Oracle SQL environments is key to efficient programming.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.