/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
A corrupted table or index is only shown as object ID in the db2diag.log file, such as “Obj={pool:6;obj:4;type:0}” for table or “Obj:{pool:15;obj:3781;type:1}” for index.
Sometimes it is necessary to know the names of those corrupted objects.
This KBA describes how to identify those corrupted table names or index names.
Read more...
Environment
SAP on IBM Db2 for Linux, UNIX, and Windows
Product
Keywords
inconsistent, corrupted, corruption, header file, how to, DIA8400C, container is not accessible, "Non-critical I/O or verification error encountered during page read from disk."ADM6006E The database manager encountered an error while reading page. ADM14001C, FODC.
, KBA , pagekey, pd_type_sqlb_page_key , BC-DB-DB6 , DB2 Universal Database for Unix / NT , 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.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)