SAP Knowledge Base Article - Preview

2773140 - How to fix error "Leaked block checking skipped due to errors" when running sp_iqcheckdb - SAP IQ

Symptom

sp_iqcheckdb('allocation database');

Stat Value Flags
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
================================================== ============================== ======
DBCC Allocation Mode Report 
================================================== ============================== ======
** DBCC Status Leaked block checking skipped due to errors ******
** DBCC Status Errors Detected ******
** DBCC Future Version Errors 12 ******

================================================== ============================== ======
Allocation Summary 
================================================== ============================== ======


Exception Thrown from dblib/db_txnInfo.cxx:343, Err# 0, tid 1551 origtid 1551
    O/S Err#: 0, ErrID: 1025 (db_catalogException); SQLCode: -1000011, SQLState: 'QDA11', Severity: 14
 [20671]: Transaction 16947095 attempted to access 'TESTTABLE' created by transaction 99999999.


Read more...

Environment

  • SAP IQ 16.0
  • SAP IQ 16.1

Keywords

sybase, sp_iqcheckdb, database, allocation, corruption, failure, dbspace, 'future version' , KBA , BC-SYB-IQ , Sybase IQ , 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.