ORA-16038/ORA-00742: Log read detects lost write in thread

ORA-16038/ORA-00742: Log read detects lost write in thread

相爱的人蒙受Oracle数据库的 REDO LOG “写错失”,变成数据库,且无法起动。

日记如下:redo log 5不只怕归档,并且侦测到“写错过”。最终致使Oracle宕机。
Errors in file
/u01/app/oracle/diag/rdbmsdbcontrol/GZDBCONTROL/trace/GZDBCONTROL_ora_32198.trc:
ORA-16038/ORA-00742: Log read detects lost write in thread。ORA-16038: log 5 sequence# 23 cannot be archived
ORA-00742: Log read detects lost write in thread %d sequence %d block
%d
ORA-00312: online log 5 thread 1:
‘/u01/app/oracle/fast_recovery_area/GZDBCONTROL/onlinelog/o1_mf_5_d61ctj3y_.log’
USER (ospid: 32198): terminating the instance due to error 16038
System state dump requested by (instance=1, osid=32198),
summary=[abnormal instance termination].
System State dumped to trace file
/u01/app/oracle/diag/rdbmsdbcontrol/GZDBCONTROL/trace/GZDBCONTROL_diag_32167_20161227110109.trc
Dumping diagnostic data in directory=[cdmp_20161227110109], requested
by (instance=1, osid=32198), summary=[abnormal instance
termination].

标题由来:
那二种清空都可能导致“写错失”爆发:操作系统、存款和储蓄系统、Oracle内部错误。

消除办法:
动用dump判别是还是不是确实爆发了“写遗失”。
SQL> alter system dump logfile
‘/u01/app/oracle/fast_recovery_area/GZDBCONTROL/onlinelog/o1_mf_5_d61ctj3y_.log’
validate;

ERROR at line 1:
ORA-00742: Log read detects lost write in thread %d sequence %d block
%d
ORA-00334: archived log:
‘/u01/app/oracle/fast_recovery_area/GZDBCONTROL/onlinelog/o1_mf_5_d61ctj3y_.log’

从上边dump的结果确认爆发了“写错失”清空,清空难题redo
logfile使其恢复生机正常归档。

SQL> alter database clear unarchived logfile group 5;

依据上述步骤,朋友的Oracle数据库寻常运营。
末段,不忘记做三遍全备份。

参考:
Database Crashe with ORA-16038/ORA-742 Errors (文档 ID 2064718.1)
亚洲必赢官网

转发请注解:
十字螺丝钉
QQ:463725310
site: www.dbhelp.net(有更加的多更新的剧情,招待访问)

E-MAIL:houora#gmail.com(#请自行替换为@)

: Log read detects lost write
in thread 朋友遇到Oracle数据库的 REDO LOG
“写遗失”,产生数据库,且无法起动。 日志如下:redo log 5无…

网站地图xml地图