DBCC checkstorage / checkverify - mismatch in number of suspect conditions detected and verified

0

I am quite new to Sybase. Recent dbcc checkstorage detected a substantial ammount of suspect conditions. A subsequent dbcc checkverify showed that it had processed only a few of them.

CHECKSTORAGE output:

DBCC CHECKSTORAGE for database '###' sequence 1712 completed at Sep 9 2019 11:04AM. 15 faults and 179699 suspect conditions were located. 0 checks were aborted. You should investigate the recorded faults, and plan a course of action that will correct them. Suspect conditions are to be treated as faults if the same suspect condition persists in subsequent CHECKSTORAGE operations, or if they are also detected by other DBCC functions.

DBCC checkverify output:

================================= DBCC CHECKVERIFY for database '###' sequence 1712 completed at Sep 9 2019 11:06AM. 2 suspect conditions considered, 0 identified as faults, 2 identified as harmless, and 0 could not be checked. 0 objects could not be checked.

Question is: why checkverify 'considered' only 2 suspect conditions if checkstorage had detected 179699 of them ? Was the rest of them that much insignificant that checkverify did not include them in the output ?

Marek

Posted 2019-09-09T10:25:53.997

Reputation: 1

No answers