locked
CHECKDB job failed RRS feed

  • Question

  • Hi All,

    The checkdb job failed with below error:

    Unspecified error occurred on SQL Server. Connection may have been terminated by the server. [SQLSTATE HY000] (Error 0) Cannot continue the execution because the session is in the kill state. [SQLSTATE HY000] (Error 596). The step failed.

    On further checking the logs, got below OS related error:

    //

    D:\DATA\DB1_Data.mdf_MSSQL_DBCC16: Operating system error 665(The requested operation could not be completed due to a file system limitation) encountered.

    The operating system returned error 665(The requested operation could not be completed due to a file system limitation) to SQL Server during a write at 
    offset 0x00006c4e40e000 in file 'D:\DATA\DB1_Data.mdf_MSSQL_DBCC16'. Additional messages in the SQL Server error log and system event log may provide more detail. 
    This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check 
    (DBCC CHECKDB). 
    This error can be caused by many factors; for more information, see SQL Server Books Online.

    DBCC CHECKDB (DB1) WITH no_infomsgs executed by GEINDSYS-AMER\502765841 terminated abnormally due to error state 6. Elapsed time: 6 hours 5 minutes 51 seconds.

    //

    Could anyone help me understand whats the issue & help with the resolution steps.

    Monday, June 22, 2020 12:01 PM

All replies

    • Proposed as answer by MIAOYUXI Tuesday, June 23, 2020 1:41 AM
    Monday, June 22, 2020 3:17 PM
  • DBCC uses snapshots internally. Snapshots are then implemented as sparse files in Windows.

    So this is actually a problem with Windows' handling of sparse files, which causes the snapshots used by DBCC to occasionally break on large and very active databases.

    refer


    https://social.technet.microsoft.com/wiki/contents/articles/37872.sql-server-installation-on-centos-linux.aspx

    Monday, June 22, 2020 3:18 PM
  • Hi SSG92,

    The link in Tom Phillips's reply is helpful.

    Helpful blog:dbcc-checkdb-job-failed-sql-server

    The error code 1450 and 665 occur to due to some storage location issue in MFT (Master File Table) and an instance known as ATTRIBUTE_LIST_ENTRY needed to maintain files in NTFS System.

    To fix this DBCC CHECKDB job failed in SQL Server due to error code 1450 and 665, need to break up the large database file into multiple files. For the Complete process, please visit the link.

    For more information about the issue, you can also visit Link.

    BR,

    MIAOYUXI


    Feel free to post your issues!

    Tuesday, June 23, 2020 2:13 AM
  • Possibly you have a high level of fragmentation in the file system. You can try the TABLOCK option of CHECKDB until you have sorted out the file system issue.

    Tibor Karaszi, SQL Server MVP (Web Blog)

    Tuesday, June 23, 2020 11:01 AM
  • Hi SSG92,

    Is the reply helpful?

    BR,

    MIAOYUXI


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Wednesday, June 24, 2020 1:30 AM