Database Crashed With ORA-16038 ORA-00742 ORA-00312 and clear unarchived logfile fails with ORA-01624 while no datafile in fuzzy state
(Doc ID 2896834.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 19.15.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
Production DB crashed with ORA-00742: Log read detects lost write in thread n sequence xxxxxx block #
ORA-00312: online log <log#> thread <thread#>: '+<Diskgroup>/<DBName>/redologfile.log'.
Database has been recovered using all the archived and available online redo log files and made sure that no datafile is in fuzzy state in v$datafile_header
Recover database is successful.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |