Database Crashed With ORA-16038 ORA-00742 ORA-00312 and clear unarchived logfile fails with ORA-01624 while no datafile in fuzzy state (文档 ID 2896834.1).pdf

不加糖

2页

1次

2024-12-23

25墨值下载

Database Crashed With ORA-16038 ORA-00742 ORA-00312 and clear unarchived logfile fails

with ORA-01624 while no datafile in fuzzy state (文档 ID 2896834.1)

In this Document

Symptoms

Changes

Cause

Solution

References

APPLIES TO:

Oracle Database - Enterprise Edition - Version 19.15.1.0.0 and later

Information 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.

RMAN> recover database;

Starting recover at 2022-09-14 23:27:56

using target database control file instead of recovery catalog

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=6 instance=<Instance> device type=DISK

starting media recovery

media recovery complete, elapsed time: 00:00:03

Finished recover at 2022-09-14 23:28:18

RMAN>

SQL> select * from v$recover_file;

no rows selected

But while trying to open the database, it fails with below error

文档显示 https://support.oracle.com/epmos/faces/SearchDocDisplay?_...

第1页共2页 2024/12/20 12:57

SQL> alter database open;

alter database open

ERROR at line 1:

ORA-00742: Log read detects lost write in thread <thread#> sequence <seq#> block <Block#>

ORA-00312: online log <log#> thread <thread#>: '+<Diskgroup>/<DBName>/redologfile.log'

While trying to perform clear unarchived logfile as mentioned in document

Doc ID 2064718.1, it fails with below error.

SQL> alter database clear unarchived logfile group <group#>;

alter database clear unarchived logfile group <group#>

ERROR at line 1:

ORA-01624: log <group#> needed for crash recovery of instance <Instance> (thread <thread#>)

ORA-00312: online log <log#> thread <thread#>: '+<Diskgroup>/<DBName>/redologfile.log'

CHANGES

CAUSE

lost write on online redo log file.

archive failed for online redo log file due to lost write on a block has been identified

SOLUTION

Recreate controlfile using trace output with noresetlogs option and then mount the database

Do a fake recovery using RMAN and then open database.

RMAN> recover database;

RMAN> alter database open;

Once the database is opened, clear the corrupted redo log file using the below statement

SQL> alter database clear unarchived logfile group <group#>;

Make sure the issue that caused the lost write is fixed and take a full backup of the database.

REFERENCES

NOTE:2064718.1

- Database Crashe with ORA-16038/ORA-742 Errors

NOTE:735106.1

- How to Recreate a Controlfile

未找到您要查找的产品?

文档显示 https://support.oracle.com/epmos/faces/SearchDocDisplay?_...

第2页共2页 2024/12/20 12:57

of 2

25墨值下载

oracle数据库

相关文档

Oracle RAC 学习笔记（可以借鉴参考）.pdf

3浏览

ORACLE数据导入导出详解.pdf

5浏览

oracle数据库坏块（物理）处理.docx

241浏览

53_Oracle Sharding.pptx

关注

云和恩墨（北京）信息技术有限公司架构师

相关文档

评论