时间:2021-07-01 10:21:17 帮助过:30人阅读
alertsid.log报错信息: Fri Sep 27 15:18:39 2013Started redo scanFri Sep 27 15:18:39 2013Errors in file /Oracle/admin/lix
alertsid.log报错信息:
Fri Sep 27 15:18:39 2013
Started redo scan
Fri Sep 27 15:18:39 2013
Errors in file /Oracle/admin/lixora/udump/lixora_ora_23439.trc:
ORA-00314: log 2 of thread 1, expected sequence# 335 doesn't match 331
ORA-00312: online log 2 thread 1: '/oracle/oradata/lixora/redo02.log'
Fri Sep 27 15:18:39 2013
Aborting crash recovery due to error 314
查看当前日志组信息:
SQL> select * From v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS
---------- ---------- ---------- ---------- ---------- --- ----------------
FIRST_CHANGE# FIRST_TIM
------------- ---------
1 1 334 52428800 1 NO ACTIVE
3613897 27-SEP-13
4 1 333 104857600 1 NO INACTIVE
3613895 27-SEP-13
3 1 336 52428800 1 NO CURRENT
3613948 27-SEP-13
2 1 335 52428800 1 NO ACTIVE
3613899 27-SEP-13
如果查询v$log发现损坏的online redo log是inactive, 说明该组日志是非当前日志, 而且已经归档完成 ( STATUS 是INACTIVE , ARCHIVE 是YES ) .
处理方法(适用于归档及非归档数据库) :
使用clear 命令清理这个文件所在的redo log group .
SQL> alter database clear logfile group 3 ;
如果该日志组还没有归档 (STATUS 是INACTIVE , ARCHIVE 是 NO )
那么需要使用如下命令
SQL> alter database clear unarchived logfile group 3 ;
然后打开数据库 , 备份 .
相关阅读:
SPFILE 错误导致数据库无法启动(ORA-01565)
ORA-01172、ORA-01151错误处理
ORA-00600 [2662]错误解决
ORA-01078 和 LRM-00109 报错解决方法
ORA-00471 处理方法笔记
,