ORA-00334 ORA-00354 ORA-00353 Corrupt redo block 8 detected: BAD BLOCK HEADER
(Doc ID 2962282.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterInformation in this document applies to any platform.
Symptoms
Archive Log Corrupted near block 8 When using OCFS2 File System as Archivelog Destination
ORA-00283: recovery session canceled due to errors
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 8 change <scn> time <Timestamp>
ORA-00334: archived log: /<path>/arc_<thread#>_<Seqno>_<nnnnnnnnn>.ARC
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 8 change <scn> time <Timestamp>
ORA-00334: archived log: /<path>/arc_<thread#>_<Seqno>_<nnnnnnnnn>.ARC
Or
Following Message on the trace file
Corrupt redo block 8 detected: BAD BLOCK HEADER
header size = 16, block size = 512
Flag: 0x1 Format: 0x22 Block: 0x<bno in hex> Seq: 0x<sequence# in hex> Beg: 0xb0 Cks:0x<checksum value in hex>
header size = 16, block size = 512
Flag: 0x1 Format: 0x22 Block: 0x<bno in hex> Seq: 0x<sequence# in hex> Beg: 0xb0 Cks:0x<checksum value in hex>
Or
Corrupt block seq: ...blocknum=8.
Bad header found during backing up archived log
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 |