Results 1 to 4 of 4
  1. #1
    Join Date
    Jun 2003
    Posts
    50

    Unanswered: dbcc checkstorage

    Hi all,

    Checked documentation and it says that these are information messages.
    Has anyone more information on what can be done to fix these

    thanks,
    dave

    sp_dbcc_runcheck "intrade_dw"
    Checking intrade_dw
    Storage checks for 'intrade_dw' are complete. DBCC is now recording the results
    in the dbccdb database.
    DBCC CHECKSTORAGE for database 'intrade_dw' sequence 116 completed at Sep 24
    2003 9:49AM. 0 faults and 3 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.
    Verifying faults for 'intrade_dw'.
    DBCC CHECKVERIFY for database 'intrade_dw' sequence 116 completed at Sep 24 2003
    9:49AM. 1 suspect conditions were resolved as faults, and 2 suspect conditions
    were resolved as harmless. 0 objects could not be checked.

  2. #2
    Join Date
    Aug 2002
    Location
    Madrid, Spain
    Posts
    97

    Re: dbcc checkstorage

    Originally posted by ddempsey
    Checked documentation and it says that these are information messages.
    DBCC CHECKVERIFY for database 'intrade_dw' sequence 116 completed at Sep 24 2003
    9:49AM. 1 suspect conditions were resolved as faults, and 2 suspect conditions
    were resolved as harmless. 0 objects could not be checked.
    The above are the messages from dbcc checkalloc and dbcc
    checkverify, and they say they finally ended with one (1)
    fault message.

    Now, you should go to (use) dbccdb and run sp_dbcc_faultreport
    to obtain the details of that fault. Refer to the Reference
    manual for syntax, and to the Troubleshooting and
    Error Messages Guide for a description of the message(s).

    The manual may suggest some risky corrective actions;
    personally, I'd wait for the next week's dbcc checkstorage
    run to see if the same message appears and points to
    the same page id. If not, it must have been a transient error
    mistakenly reported as a "verified" fault.

    Regards,
    Mariano Corral

  3. #3
    Join Date
    Feb 2002
    Location
    Willy is on vacation
    Posts
    1,208
    or you can run dbcc checkverify(dbanme) after the fault report and confirm if the errors are genuine.

  4. #4
    Join Date
    Aug 2002
    Location
    Madrid, Spain
    Posts
    97

    or you can run dbcc checkverify(dbanme) after the fault report and confirm if the errors are genuine.
    He did it, so the fault is as genuine as dbcc checkverify
    can tell. For what I've seen before, even dbcc checkverify may
    report false faults. This is why I suggested a second run.

    Regards,
    Mariano Corral

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •