Symptom
Database reports a inconsistent following a Database and OS restart
Db2diag.log reports database inconsistencies and an offline tablespace
Errors like
MESSAGE: Crash recovery is needed
MESSAGE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not exist"
DIA8506C Unexpected end of file was reached.
DATA #1 : <preformatted>
Failed to read page from disk on attempt number <nr>.
Retrying operation. Only subsequent failures will be logged.
MESSAGE : ADM6006E DB2 encountered an error while reading page "XXXXXX" from
table space "X" for object "XXXXX" (located at offset "XXXXX" of
container "/db2/<SID>/sapdataXX/NODE0000/<SID>#XXXX.containerXXX").
MESSAGE : Error during REDO of log record:
MESSAGE : SQLB_NOT_ALLOWED_OFFLINE
"Access not allowed. Tblspc Offline."
DATA #1 : <preformatted>
Tablespace X : state= 0x4080, action= X.
Read more...
Environment
Db2 LUW IBM
Product
Keywords
FODC, Crash, Corruption, restore, inconsistency , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem
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.