Symptom
I. During a Recovery process of a Single Instance Database
or
in a Data Guard/ DR /Standby Database
or
during a System Refresh
one of the following messages occurs:
-
DBV shows the following error:
BR0398W DBVERIFY has detected corrupt blocks
DBV-00201: Block, DBA 1154567432, marked corrupt for invalid redo
application - V$DATABASE_BLOCK_CORRUPTION contains such a row:
9 5 129573 4 3253280299 NOLOGGING
INDPART SAPTAP /BIC/FZD_BACK2~080 /BIC/FZD_BACK20
II. Or you observe the following messages in Oracle Alert Log
ORA-01578: ORACLE data block corrupted (file # 343, block # 383621)
ORA-01110: data file 343: '/oracle/BP1/sapdata21/sr3_326/sr3.data326'
ORA-26040: Data block was loaded using the NOLOGGING option
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Here the last ORA- message is very important!
Read more...
Environment
- SAP Release independent
- Oracle Database Release independent
- Oracle Single Instance Database
- Oracle DataGuard /DR / Standby Database
- Operating System independent
Keywords
Logging while Index,SPRO,IMG,corruption,RMAN,DBV,ANALYZE,verification,check,consistency,ORA-26040,DBV-00201,DBV-201,soft corruption,nologging,dbv,rman,datapump,data pump,expdp,impdp,exp,imp,blockcorruption,block corruption, Data Guard, dataguard, disaster recovery, dr, primary, standby, logging, table, index, LOB, migration, unicode , KBA , BW-SYS-DB-ORA , BW ORACLE , BC-DB-ORA , Oracle , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.