Post reply

CheckDB message

  • May 12, 2017 at 8:18 am

    #336869

    Hi

    I've received the following error messages as a result of a regular checkDB. They're not very helpful.  Can anyone suggest a way forward?

    Msg 802, Level 17, State 20, Server SQL01, Line 1
    Error: 802, Severity: 17, State: 20. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.

    Msg 8921, Level 16, State 1, Server SQL01, Line 1
    Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.

    Regards

    Alex

  • May 12, 2017 at 9:05 am

    #1942356

    Have you checked the size of your temp DB.

    Here is a related report of this and a good set of conversations https://social.msdn.microsoft.com/Forums/sqlserver/en-US/6548a457-7c46-4012-9892-432be9d391d8/error-message-when-i-do-dbcc-checkdb?forum=sqldatabaseengine

  • May 12, 2017 at 9:46 am

    #1942364

    alex.palmer - Friday, May 12, 2017 8:18 AM

    Hi

    I've received the following error messages as a result of a regular checkDB. They're not very helpful.  Can anyone suggest a way forward?

    Msg 802, Level 17, State 20, Server SQL01, Line 1
    Error: 802, Severity: 17, State: 20. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.

    Msg 8921, Level 16, State 1, Server SQL01, Line 1
    Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.

    Regards

    Alex

    802 is insufficient memory - have you checked your memory settings?

    Sue

  • May 15, 2017 at 1:46 am

    #1942478

    Hi

    Thanks for the replies.

    I looked in the SQL log and it looks like there was a memory issue at the time. This "LazyWriter: warning, no free buffers found." was on of the many errors logged

    I ran a dbcc checkdb with no_infomsgs all_errormsgs on the database that it bombed out on and no problems reported.

    So the good news is that is doesn't look like I've got any corruption.

    Cheers
    Alex

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply