Solution : https://service.sap.com/sap/support/notes/547464 (SAP Service marketplace login required)
Summary :
In SAP systems, enabling 'nologging' during index creation reduces logging overhead, accelerating the process and decreasing archivelogs, which simplifies backup and recovery operations. However, post-recovery, such indexes may need recreation if not logged initially, causing potential data integrity issues, evidenced by Oracle errors like ORA-01578 or ORA-26040. To address this, recovery scripts are provided to identify and rectify affected indexes, crucial for maintaining robust data integrity and minimizing downtime in SAP BW environments. Note that continuous performance post-index creation does involve logging, safeguarding ongoing transactions.
Key words :
terms nologging software corrupt blocks backup strategy recovery strategy backupstrategy recoverystrategy ora-01578 ora-26040 dbv-00201 reason, --- backup ------------- --- indexcreation 0 ---- --- indexcreation 1 -------- --- indexcreation 2 -------- --- indexcreation 3 ---------------------t-----------------------------------------> timet, --[ t1 ]----[ t2 ]---------------------------t3-----------> time backup indexcreation, block_id + blocks -1from dba_extentswhere owner = <owner>, segment_name = <segment_name> andpartition_name = <partition_name> order, block type = found block, alter database <sid> force logging, system back completely working, dbv-00201 marked corrupt, sorted corrupt blocks detected
Related Notes :
| 1395074 | ORA-00201: Block, dba <address>, marked corrupt for invalid |
| 842240 | FAQ: Backup strategy of large and highly-available databases |
| 806554 | FAQ: I/O-intensive database operations |
| 442763 | Avoid NOLOGGING during the index structure (Oracle) |