DBCC CHECKDB error

  • Nightly backup and integrity check maintenance plan threw this error last night:

    Failed:(-1073548784) Executing the query "DBCC CHECKDB(N'WSS_Content_CLIENTS') WITH NO_INFO..." failed with the following error: "Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

    Reran the command manually, no errors.

    Checked tempdb settings and space - tempdb db/logs set to autogrow. Disk has 70GB free.

    Ran DBCC CHECKDB('WSS_Content_CLIENTS') WITH ESTIMATEONLY and it returns:

    Estimated TEMPDB space needed for CHECKALLOC (KB)

    -------------------------------------------------

    11837

    (1 row(s) affected)

    Estimated TEMPDB space needed for CHECKTABLES (KB)

    --------------------------------------------------

    19

    (1 row(s) affected)

    DBCC execution completed. If DBCC printed error messages, contact your system administrator.

    Ran WITH ESTIMATEONLY for all other dbs and the largest needed space is 36435 kb.

    Hardly a space problem. Any ideas why it threw this error?

  • The error is:

    Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent

    It's usually the latter in my experience. Can you run the following and post the full and complete results?

    DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

    Got a backup?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • DBCC CHECKDB ('WSS_Content_CLIENTS') WITH NO_INFOMSGS, ALL_ERRORMSGS

    Command(s) completed successfully.

    Nada.

  • Then probably TempDB really was low on space (Estimate_Only is an estimate and iirc there's problem with it).

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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