Solution : https://service.sap.com/sap/support/notes/365481 (SAP Service marketplace login required)
Summary :
When encountering corrupt blocks with Oracle error messages such as ORA-01578 or ORA-00600, it can typically stem from underlying hardware or system issues rather than Oracle itself. Corruption typically cannot be fixed via Restore/Recovery methods, implying the need for alternative resolutions such as index recreation, particularly under 'nologging' conditions in BW systems. SAP Note 547464 and FAQ Note 540463 provide additional guidance on managing such corruptions, recommending full database checks per Note 23345, ensuring hardware integrity, and detailed documentation of remediation steps. Techniques involve identifying corrupt blocks, replacing files, or reorganizing tablespaces using tools like brspace.
Key words :
alter system dump datafile <file_id> block min <lowest block_id> block max <highest block_id>, alter system dump datafile 59 block 118882, 'analyze table validate structure cascade online', alter table <tablename> deallocate unused, alter system dump datafile <file#, 'analyze table validate structure cascade', table/index cross reference failure -, rollback segment-specific underscore parameters, corrupted block> block<corrupted block>, rare cases oracle bugs
Related Notes :
1395074 | ORA-00201: Block, dba <address>, marked corrupt for invalid |
1144558 | ORA-08103 or ORA-01410 in connection with DROPs |
1116190 | Handling of database corruptions by the SAP Support |
764015 | Segment corruption in ASSM tablespace |
724972 | ORA-00200: Block, dba <address>, already marked corrupted |
605062 | FAQ: Restore and recovery |
591600 | Error due to inappropriate column values |
546006 | Problems with Oracle due to operating system errors |
540463 | FAQ: Consistency Checks + Block Corruptions |
434645 | Point-in-time recovery: What must I be aware of? |
354293 | DBVerify reports corrupt block in freespace area |
96296 | CC-ERROR: Database problem in client copy |
31496 | CC-INFO: Client deleted by mistake |
23345 | Consistency check of ORACLE database |
4190 | Recovery for defective rollback segments |
4161 | Complete recovery |