Re: Now what!! ORA-00313 open falied for members! Help

In article <m35g3u09sei9ct4cqtan1pe093glm661ri_at_4ax.com>, Kev says...
>
>Ok, I dont get it. I just resized the log files. Everything went
>fine no errors. Then about 4 hours later I got these errors.
>---------------------------------------------------------------------------------------------
>Errors in file E:\oracle\admin\k2\bdump\k2LGWR.TRC:
>ORA-00313: open failed for members of log group 1 of thread 1
>
>Sun Jan 06 00:09:46 2002
>Errors in file E:\oracle\admin\k2\bdump\k2LGWR.TRC:
>ORA-00313: open failed for members of log group 3 of thread 1
>
>Sun Jan 06 00:09:46 2002
>Errors in file E:\oracle\admin\k2\bdump\k2LGWR.TRC:
>ORA-00313: open failed for members of log group 4 of thread 1
>
>Sun Jan 06 00:09:46 2002
>Errors in file E:\oracle\admin\k2\bdump\k2LGWR.TRC:
>ORA-00313: open failed for members of log group 3 of thread 1
>----------------------------------------------------------------------------------------------
>

care to share any meaningful text that might be found in the above referenced trace files?

>Here are the commands I used to create the log file:
>
>alter database add logfile group 4 'E:\ORACLE\ORADATA\K2\REDO04a.log'
>size 10M;
>
>alter system switch logfile;
>
>Then I dropped group 1
>
>alter database add logfile group 1 'H:\ORADATA\REDO01a.log' size 10M;
>
>switched again then dropped 3
>
>alter database add logfile group 3 'C:\ORADATA\REDO03a.log' size 10M;
>
>
>Why did this error occur???
>
>The files do exists and the path is correct. When I query the v$log
>table I get the 3 files and the group 1,3,4. The Orginal groups were
>1,2,3.
>
>And the paths match fine.
>
>What happened???
>
>Thanks again,
>
>Kev

--
Thomas Kyte (tkyte@us.oracle.com)             http://asktom.oracle.com/ 
Expert one on one Oracle, programming techniques and solutions for Oracle.
http://www.amazon.com/exec/obidos/ASIN/1861004826/  
Opinions are mine and do not necessarily reflect those of Oracle Corp