Brian, Adding on the responses already given. I'll suggest workaround creating a whole new redo log group in another location, then switch inmediately to use it. Once the old log group is not used by Oracle, you can safely drop it .(via ALTER DATABASE DROP LOGFILE GROUP) regards This error occured on Windows Server 2003 while the weekly backup (Symantec) was running. Anyone have any ideas why this occurred and as possible work areound?