Database Crashe with ORA-16038/ORA-742 Errors

刘泽宇

现象：
Database down with below errors ....

Thu Sep 17 08:58:18 2015
Errors in file ...trace\xxxx_ora_4376.trc:
ORA-16038: log 3 sequence# 534 cannot be archived
ORA-00742: Log read detects lost write in thread sequence block
ORA-00312: online log 3 thread 1: 'E:\ARCHIVELOGS\xxx\REDO03.LOG'
USER (ospid: 4376): terminating the instance due to error 16038
Thu Sep 17 08:58:18 2015
ARC0: STARTING ARCH PROCESSES
Thu Sep 17 08:58:19 2015
System state dump requested by (instance=1, osid=4376), summary=[abnormal instance termination].
System State dumped to trace file ...trace\xxxx_diag_3208.trc
Dumping diagnostic data in directory=[cdmp_20150917085819], requested by (instance=1, osid=4376), summary=[abnormal instance termination].
Thu Sep 17 08:58:21 2015
Instance terminated by USER, pid = 4376



原因：
REDO03.LOG was lost .

The ora-742 says there was a lost write to REDO03.LOG .


处理方法：
SQL> alter system dump logfile 'E:\ARCHIVELOGS\xxx\REDO03.LOG' validate;


Clear the log in order to enable the archival again


SQL> select group#,member from v$logfile;
SQL> alter database clear unarchived logfile group <group number>;

Should be group# 3 , if yes

After this ,  take a full backup, because the old one would not be useful anymore because of the lost of archive log sequence .