- Using the SAP IQ stored procedure sp_iqcheckdb to run a DBCC database consistency check against a database object can take a long time to run.
- The DBCC will scan all blocks of the database object and only report on how many are corrupt at the end of the scan.
- Continuing to scan an object that a corrupt block has been found for may be unnecessary and can increase the run time of sp_iqcheckdb.
- This enhancement requirement is to have an option to stop the scan after the first corrupt block is encountered for an object and allow processing to continue on the next object.
- SAP IQ version 16.0 sp11.x on all platfroms prior to patch level PL07
CR 803543, CR# 803543, 803543, 'check table' , NFR, performance, checker, verify, allocation, consistent, sybase, invalid, corruption, inconsistent, checkdb, slow, error, feature, 'new feature' , KBA , BC-SYB-IQ , Sybase IQ , Product Enhancement
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.