ORA-00313 ORA-00312 redo日志报错怎么处理

小编给大家分享一下ORA-00313 ORA-00312 redo日志报错怎么处理，相信大部分人都还不怎么了解，因此分享这篇文章给大家参考一下，希望大家阅读完这篇文章后大有收获，下面让我们一起去了解一下吧！

1、前台启动数据库报错

SQL> alter database open;

alter database open

*

ERROR at line 1:

ORA-03113: end-of-file on communication channel

Process ID: 18809

Session ID: 1 Serial number: 50801

2、后台alter$ORACLE_SID.log 报错

alter database open

2017-09-16T21:38:38.117453+08:00

Ping without log force is disabled:

  instance mounted in exclusive mode.

Endian type of dictionary set to little

2017-09-16T21:38:38.136378+08:00

Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_lgwr_18769.trc:

ORA-00313: open failed for members of log group 7 of thread 1

ORA-00312: online log 7 thread 1: /u01/app/oracle/oradata/ORCL/onlinelog/redolog12.log

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 7

ORA-00312: online log 7 thread 1: /u01/app/oracle/oradata/ORCL/onlinelog/redolog8.log

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 7

2017-09-16T21:38:38.136457+08:00

Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_lgwr_18769.trc:

ORA-00313: open failed for members of log group 7 of thread 1

ORA-00312: online log 7 thread 1: /u01/app/oracle/oradata/ORCL/onlinelog/redolog12.log

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 7

ORA-00312: online log 7 thread 1: /u01/app/oracle/oradata/ORCL/onlinelog/redolog8.log

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 7

2017-09-16T21:38:38.137207+08:00

Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_18809.trc:

ORA-00313: open failed for members of log group 1 of thread 

ORA-00312: online log 7 thread 1: /u01/app/oracle/oradata/ORCL/onlinelog/redolog8.log

ORA-00312: online log 7 thread 1: /u01/app/oracle/oradata/ORCL/onlinelog/redolog12.log

2017-09-16T21:38:38.152526+08:00

TT00: Gap Manager starting (PID:19017)

2017-09-16T21:38:38.168038+08:00

USER (ospid: 18809): terminating the instance due to error 313

2017-09-16T21:38:38.253720+08:00

System state dump requested by (instance=1, osid=18809), summary=[abnormal instance termination].

System State dumped to trace file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_diag_18751_20170916213838.trc

2017-09-16T21:38:38.393632+08:00

Dumping diagnostic data in directory=[cdmp_20170916213838], requested by (instance=1, osid=18809), summary=[abnormal instance termination].

2017-09-16T21:38:39.702685+08:00

Instance terminated by USER, pid = 18809

处理办法：

清除归档日志

alter database clear unarchived logfile group 7;

--alter database clear unarchived logfile group 2;

--alter database clear unarchived logfile group 3;

alter database open;

以上是“ORA-00313 ORA-00312 redo日志报错怎么处理”这篇文章的所有内容，感谢各位的阅读！相信大家都有了一定的了解，希望分享的内容对大家有所帮助，如果还想学习更多知识，欢迎关注行业资讯频道！