0 Replies Latest reply on Jun 26, 2017 1:02 AM by 1224761

    Database instance terminating after throwing Error ORA-00742: Log read detects lost write in thread 1

    1224761

      Hi,

       

      I am facing database termination issue on my Development database servers very now and then.
      Below is what I see in alert log :

      =========================

      ARC3: Closing local archive destination LOG_ARCHIVE_DEST_1: '/oravl01/oracle/adm/TESTDB/arc/archTESTDB_29623_1_884435796.dbf' (error 742) (TESTDB)

      Sun Jun 25 02:26:27 2017

      Errors in file /oravl01/oracle/adm/TESTDB/diag/rdbms/testdb/TESTDB/trace/TESDB_arc0_11714.trc:

      ORA-00742: Log read detects lost write in thread 1 sequence 29623 block 56671

      ORA-00312: online log 3 thread 1: '/oravl05/oradata/TESTDB/redo_g3_m2.dbf'

      ORA-00312: online log 3 thread 1: '/oravl05/oradata/TESTDB/redo_g3_m1.dbf'

      Sun Jun 25 02:26:27 2017

      ARC0: All Archive destinations made inactive due to error 742

      Sun Jun 25 02:26:27 2017

      ARC0: Closing local archive destination LOG_ARCHIVE_DEST_1: '/oravl01/oracle/adm/TESTDB/arc/archTESTDB_29623_1_884435796.dbf' (error 742) (TESTDB)

      ********************* ATTENTION: ********************

      The controlfile header block returned by the OS

      has a sequence number that is too old.

      The controlfile might be corrupted.

      PLEASE DO NOT ATTEMPT TO START UP THE INSTANCE

      without following the steps below.

      RE-STARTING THE INSTANCE CAN CAUSE SERIOUS DAMAGE

      TO THE DATABASE, if the controlfile is truly corrupted.

      In order to re-start the instance safely,

      please do the following:

      (1) Save all copies of the controlfile for later

           analysis and contact your OS vendor and Oracle support.

      (2) Mount the instance and issue:

           ALTER DATABASE BACKUP CONTROLFILE TO TRACE;

      (3) Unmount the instance.

      (4) Use the script in the trace file to

           RE-CREATE THE CONTROLFILE and open the database.

      *****************************************************

      Sun Jun 25 02:26:27 2017

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

      System State dumped to trace file /oravl01/oracle/adm/TESTDB/diag/rdbms/testdb/TESTDB/trace/TESTDB_diag_11671_20170625022627.trc

      Sun Jun 25 02:26:27 2017

      ARC0 (ospid: 11714): terminating the instance

      Sun Jun 25 02:26:28 2017

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

      Sun Jun 25 02:26:28 2017

      Instance terminated by ARC0, pid = 11714

      Mon Jun 26 05:42:42 2017

      Starting ORACLE instance (normal) (OS id: 13882)

      Mon Jun 26 05:42:42 2017

      CLI notifier numLatches:11 maxDescs:4151

      Mon Jun 26 05:42:42 2017

      **********************************************************************

       

      ORACLE DB version : 12.1.0.2 - Enterprise edition

      OS : Red Hat Enterprise Linux Server release 7.2 (Maipo)