I am getting an Ora-00742 error on Windows with Oracle 12c when I try to startup a database instance. Can anyone advise how to handle?
SQL> startup
ORACLE instance started.
Total System Global Area 1670221824 bytes
Fixed Size 2403352 bytes
Variable Size 1006633960 bytes
Database Buffers 654311424 bytes
Redo Buffers 6873088 bytes
Database mounted.
ORA-00742: Log read detects lost write in thread 1 sequence 162 block 5976
ORA-00312: online log 3 thread 1: 'D:\APP\ORACLE\ORADATA\ORCL\REDO03.LOG'
Oracle's advice for this error is:
Oracle error message – ORA-00742: Log read detects lost write in thread string sequence string block string
Root Cause: Either a write issued by Oracle was lost by the underlying operating system or storage system or an Oracle internal error occurred.
Solution: To fix the above error, Action: The trace file shows the lost write location. Dump the problematic log file to see whether it is a real lost write. Contact Oracle Support Services.
Alert Log says:
Fri Apr 04 05:21:42 2014
Started redo scan
Fri Apr 04 05:21:43 2014
Slave encountered ORA-10388 exception during crash recovery
Fri Apr 04 05:21:43 2014
Slave encountered ORA-10388 exception during crash recovery
Fri Apr 04 05:21:43 2014
Slave encountered ORA-10388 exception during crash recovery
Fri Apr 04 05:21:43 2014
Aborting crash recovery due to error 742
Fri Apr 04 05:21:43 2014
Errors in file D:\APP\ORACLE\diag\rdbms\orcl\orcl\trace\orcl_ora_8160.trc:
ORA-00742: Log read detects lost write in thread 1 sequence 162 block 5976
ORA-00312: online log 3 thread 1: 'D:\APP\ORACLE\ORADATA\ORCL\REDO03.LOG'
Fri Apr 04 05:21:43 2014
Errors in file D:\APP\ORACLE\diag\rdbms\orcl\orcl\trace\orcl_ora_8160.trc:
ORA-00742: Log read detects lost write in thread 1 sequence 162 block 5976
ORA-00312: online log 3 thread 1: 'D:\APP\ORACLE\ORADATA\ORCL\REDO03.LOG'
ORA-742 signalled during: ALTER DATABASE OPEN...
Fri Apr 04 05:36:40 2014
db_recovery_file_dest_size of 6930 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
The Trace says:
*** 2014-04-04 05:21:43.269
WARNING! lost write detected in log 3(thread 1 seq 162 block 5976). On disk rba is 0x0000a2.0000177e.0000
Dump the log block header:
Flag: 0x1 Format: 0x22 Block: 0x00001758 Seq: 0x0000009f Beg: 0xb8 Cks:0xe81e
Flag: 0x1 Format: 0x22 Block: 0x00001759 Seq: 0x0000009f Beg: 0xd0 Cks:0x36d8
Flag: 0x1 Format: 0x22 Block: 0x0000175a Seq: 0x0000009f Beg: 0x10 Cks:0xcfcf
Flag: 0x1 Format: 0x22 Block: 0x0000175b Seq: 0x0000009f Beg: 0x28 Cks:0x5ad7
Flag: 0x1 Format: 0x22 Block: 0x0000175c Seq: 0x0000009f Beg: 0x40 Cks:0x3bd2
... Thousands of lines like this
Flag: 0x1 Format: 0x22 Block: 0x00003739 Seq: 0x0000009f Beg: 0x10 Cks:0xb447
Flag: 0x1 Format: 0x22 Block: 0x0000373a Seq: 0x0000009f Beg: 0x10 Cks:0x226c
DDE rules only execution for: ORA 312
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00742: Log read detects lost write in thread 1 sequence 162 block 5976
ORA-00312: online log 3 thread 1: 'D:\APP\ORACLE\ORADATA\ORCL\REDO03.LOG'
ORA-00742: Log read detects lost write in thread 1 sequence 162 block 5976
ORA-00312: online log 3 thread 1: 'D:\APP\ORACLE\ORADATA\ORCL\REDO03.LOG'