Solution : https://service.sap.com/sap/support/notes/694155 (SAP Service marketplace login required)
Summary :
This SAP Note addresses errors related to Oracle redo log corruption, highlighting the lack of support for repairing such inconsistencies which are typically triggered by hardware issues. The note explains scenarios where recovery of archiving operations fail due to these errors, leading to transaction inconsistencies or the inability to perform complete recoveries. Solution strategies include checking for successful recovery of online and offline redo logs, using alternative backups, avoiding deprecated practices, and ensuring double-copy archiving. It also recommends validating redo log consistency using RMAN and provides specific guides on managing various error scenarios such as ORA-00600 [3020] and addressing potential data file corruption.
Key words :
block <block> change <scn> time <time>ora-00354, recommended copy delete save archiving process, alter database clear unarchived logfile '<log>', corrupt redo log block headerora-00355, perform additional manual steps, relevant offline redo log, actual data file corruption, obsolete data file version, error archiving log, hot standby database
Related Notes :
| 1016173 | Verifying database and archive log files using RMAN |
| 553526 | Recovery terminates with ORA-600 [3020] |
| 540463 | FAQ: Consistency Checks + Block Corruptions |
| 492580 | ORA-600 [3020] |
| 394018 | Oracle & Direct IO on Tru64 UNIX V5.X |
| 4162 | Missing "end backup" |
| 391 | Archiver stuck |