none
CHECKDB found 0 allocation errors and 8 consistency errors in table (object ID 1698105090). CHECKDB found 0 allocation errors and 23 consistency errors in database ''.

    Question

  • Hi,

    My SQL Server 2008 is on VMWare and i got below error for database inconsistency errors. This is the second time i m getting this consistency error for the same database. Previously i was getting my checkpoint stuck for same database of size 60 GB and failing my backups. Then to resolve issue at instant time i created a checkpoint job executing it every 3 hours. Now after fortnight i am getting corruption issues on my databases.

    Kindly suggest me why this is happening for the same database again and again and what can be the root cause. Kindly find the server configuration and errors i got on my Server. I executed DBCC checkdb on mentioned database and error reported are pasted below. Please help and reply if and more details required.

    Server Configuration:

    Windows Server 2008 R2 enterprise edition

    Ram : 10 GB

    SQL Server 2008 R2 standard edition SP2 64 bit Version: 10.50.4260.0

    Error 1:

    SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x90201477; actual: 0xf834dbc5). It occurred during a read of page (6:3961787) in database ID 8 at offset 0x0000078e776000 in file 'F:\Database\DW_MilesUAT\DW_Edelweiss_Fact.ndf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe 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.
    Error: 824, Severity: 24, State: 2.
    SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x90201477; actual: 0xf834dbc5). It occurred during a read of page (6:3961787) in database ID 8 at offset 0x0000078e776000 in file 'F:\Database\DW_MilesUAT\DW_Edelweiss_Fact.ndf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe 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.
    Error: 824, Severity: 24, State: 2.
    SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x90201477; actual: 0xf834dbc5). It occurred during a read of page (6:3961787) in database ID 8 at offset 0x0000078e776000 in file 'F:\Database\DW_MilesUAT\DW_Edelweiss_Fact.ndf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe 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 Error:

    Msg 8909, Level 16, State 1, Line 1
    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (6:5701883)
    contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
    Msg 8909, Level 16, State 1, Line 1
    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (6:5701887)
    contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
    Msg 8909, Level 16, State 1, Line 1
    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281475513581568 (type Unknown), page ID (6:5135934)
     contains an incorrect page ID in its page header. The PageId in the page header = (1:-1065590784).
    CHECKDB found 0 allocation errors and 3 consistency errors not associated with any single object.
    Msg 8928, Level 16, State 1, Line 1
    Object ID 1042102753, index ID 1, partition ID 72057594046382080, alloc unit ID 72057594111918080 (type In-row data): Page (6:5135934) could not be processed.  See other errors for details.
    Msg 8976, Level 16, State 1, Line 1
    Table error: Object ID 1042102753, index ID 1, partition ID 72057594046382080, alloc unit ID 72057594111918080 (type In-row data). Page (6:5135934) was not seen in the scan although its parent (6:5136210) and previous (6:5135933) refer to it. Check any previous errors.
    Msg 8978, Level 16, State 1, Line 1
    Table error: Object ID 1042102753, index ID 1, partition ID 72057594046382080, alloc unit ID 72057594111918080 (type In-row data). Page (6:5135935) is missing a reference from previous page (6:5135934). Possible chain linkage problem.
    Msg 8928, Level 16, State 1, Line 1
    Object ID 1042102753, index ID 1, partition ID 72057594046382080, alloc unit ID 72057594111918080 (type In-row data): Page (6:5701883) could not be processed.  See other errors for details.
    Msg 8976, Level 16, State 1, Line 1
    Table error: Object ID 1042102753, index ID 1, partition ID 72057594046382080, alloc unit ID 72057594111918080 (type In-row data). Page (6:5701883) was not seen in the scan although its parent (6:5702184) and previous (6:5701882) refer to it. Check any previous errors.
    Msg 8928, Level 16, State 1, Line 1
    Object ID 1042102753, index ID 1, partition ID 72057594046382080, alloc unit ID 72057594111918080 (type In-row data): Page (6:5701884) could not be processed.  See other errors for details.
    Msg 8939, Level 16, State 98, Line 1
    Table error: Object ID 1042102753, index ID 1, partition ID 72057594046382080, alloc unit ID 72057594111918080 (type In-row data), page (6:5701884). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.
    Msg 8980, Level 16, State 1, Line 1
    Table error: Object ID 1042102753, index ID 1, partition ID 72057594046382080, alloc unit ID 72057594111918080 (type In-row data). Index node page (6:5702184), slot 55 refers to child page (6:5701884) and previous child (6:5701883), but they were not encountered.
    Msg 8978, Level 16, State 1, Line 1
    Table error: Object ID 1042102753, index ID 1, partition ID 72057594046382080, alloc unit ID 72057594111918080 (type In-row data). Page (6:5701885) is missing a reference from previous page (6:5701884). Possible chain linkage problem.
    Msg 8928, Level 16, State 1, Line 1
    Object ID 1042102753, index ID 1, partition ID 72057594046382080, alloc unit ID 72057594111918080 (type In-row data): Page (6:5701887) could not be processed.  See other errors for details.
    Msg 8976, Level 16, State 1, Line 1
    Table error: Object ID 1042102753, index ID 1, partition ID 72057594046382080, alloc unit ID 72057594111918080 (type In-row data). Page (6:5701887) was not seen in the scan although its parent (6:5702184) and previous (6:5701886) refer to it. Check any previous errors.
    Msg 8978, Level 16, State 1, Line 1
    Table error: Object ID 1042102753, index ID 1, partition ID 72057594046382080, alloc unit ID 72057594111918080 (type In-row data). Page (6:5701888) is missing a reference from previous page (6:5701887). Possible chain linkage problem.
    CHECKDB found 0 allocation errors and 12 consistency errors in table '************' (object ID 1042102753).
    Msg 8928, Level 16, State 1, Line 1
    Object ID 1698105090, index ID 1, partition ID 72057594048151552, alloc unit ID 72057594112507904 (type In-row data): Page (6:1634032) could not be processed.  See other errors for details.
    Msg 8939, Level 16, State 98, Line 1
    Table error: Object ID 1698105090, index ID 1, partition ID 72057594048151552, alloc unit ID 72057594112507904 (type In-row data), page (6:1634032). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.
    Msg 8976, Level 16, State 1, Line 1
    Table error: Object ID 1698105090, index ID 1, partition ID 72057594048151552, alloc unit ID 72057594112507904 (type In-row data). Page (6:1634032) was not seen in the scan although its parent (6:1912188) and previous (6:1604872) refer to it. Check any previous errors.
    Msg 8928, Level 16, State 1, Line 1
    Object ID 1698105090, index ID 1, partition ID 72057594048151552, alloc unit ID 72057594112507904 (type In-row data): Page (6:1634035) could not be processed.  See other errors for details.
    Msg 8939, Level 16, State 98, Line 1
    Table error: Object ID 1698105090, index ID 1, partition ID 72057594048151552, alloc unit ID 72057594112507904 (type In-row data), page (6:1634035). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.
    Msg 8976, Level 16, State 1, Line 1
    Table error: Object ID 1698105090, index ID 1, partition ID 72057594048151552, alloc unit ID 72057594112507904 (type In-row data). Page (6:1634035) was not seen in the scan although its parent (6:1608965) and previous (6:1613689) refer to it. Check any previous errors.
    Msg 8978, Level 16, State 1, Line 1
    Table error: Object ID 1698105090, index ID 1, partition ID 72057594048151552, alloc unit ID 72057594112507904 (type In-row data). Page (6:1647482) is missing a reference from previous page (6:1634035). Possible chain linkage problem.
    Msg 8978, Level 16, State 1, Line 1
    Table error: Object ID 1698105090, index ID 1, partition ID 72057594048151552, alloc unit ID 72057594112507904 (type In-row data). Page (6:1654159) is missing a reference from previous page (6:1634032). Possible chain linkage problem.
    CHECKDB found 0 allocation errors and 8 consistency errors in table '*************' (object ID 1698105090). CHECKDB found 0 allocation errors and 23 consistency errors in database '##########'.
    repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (############).

    Friday, June 28, 2013 3:27 PM

All replies

  • do u have a backup, restore and check. otherwise, may lose some data with

    DBCC CHECKTABLE ('Tablename', REPAIR_ALLOW_DATA_LOSS) 

    http://www.sqlservercentral.com/Forums/Topic1232926-2893-1.aspx#bm1233046

    Sunday, June 30, 2013 8:06 AM
  • I have executed DBCC CHECKTABLE ('Tablename', REPAIR_ALLOW_DATA_LOSS) because i dont have the backup. I am not concern about the data loss because this is not production but users are not able to work because of data inconsistency on the table.

    I am concerned about why this is happening again and again on same database. Again today morning i got inconsistency error on same database. And my hardware vendor also check all disk consistency and hardware related analysis and he confirmed that everything is working fine.

    Please help me and why this is happening again and again. And find below the error i got today morning.

    Errorlog:

    SQL Server has encountered 3 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [F:\TempDb\tempLog.ldf] in database [tempdb] (2).  The OS file handle is 0x0000000000000574.  The offset of the latest long I/O is: 0x000000f56fa00
    DBCC CHECKDB (DW_MilesUAT) executed by sqldba found 0 errors and repaired 0 errors. Elapsed time: 0 hours 40 minutes 42 seconds.  Internal database snapshot has split point LSN = 0001ea0f:000064ac:02d0 and first LSN = 0001ea0f:000028e6:0278.
    Operating system error 'incorrect checksum (expected: 0x1a21ec4c; actual: 0x1a21ec4c)' resulted from attempt to read the following: sort run page (1:63317), in file 'E:\TempDB\tempdev.mdf', in database with ID 2. Sort is retrying the read.
    Error: 823, Severity: 24, State: 7.
     The operating system returned error incorrect checksum (expected: 0x1a21ec4c; actual: 0x1a21ec4c) to SQL Server during a read at offset 0x0000001eeaa000 in file 'E:\TempDB\tempdev.mdf'. Additional messages in the SQL Server error log and system event log m

    DBCC checkdb:

    DBCC results for 'BI.FT_Equity_Holding'.
    Msg 8928, Level 16, State 1, Line 1
    Object ID 1042102753, index ID 1, partition ID 72057594064207872, alloc unit ID 72057594115194880 (type In-row data): Page (6:5704546) could not be processed.  See other errors for details.
    Msg 8976, Level 16, State 1, Line 1
    Table error: Object ID 1042102753, index ID 1, partition ID 72057594064207872, alloc unit ID 72057594115194880 (type In-row data). Page (6:5704546) was not seen in the scan although its parent (6:5704811) and previous (6:5704545) refer to it. Check any previous errors.
    Msg 8928, Level 16, State 1, Line 1
    Object ID 1042102753, index ID 1, partition ID 72057594064207872, alloc unit ID 72057594115194880 (type In-row data): Page (6:5704547) could not be processed.  See other errors for details.
    Msg 8980, Level 16, State 1, Line 1
    Table error: Object ID 1042102753, index ID 1, partition ID 72057594064207872, alloc unit ID 72057594115194880 (type In-row data). Index node page (6:5704811), slot 89 refers to child page (6:5704547) and previous child (6:5704546), but they were not encountered.
    Msg 8978, Level 16, State 1, Line 1
    Table error: Object ID 1042102753, index ID 1, partition ID 72057594064207872, alloc unit ID 72057594115194880 (type In-row data). Page (6:5704548) is missing a reference from previous page (6:5704547). Possible chain linkage problem.
    Msg 8928, Level 16, State 1, Line 1
    Object ID 1042102753, index ID 1, partition ID 72057594064207872, alloc unit ID 72057594115194880 (type In-row data): Page (6:5704559) could not be processed.  See other errors for details.
    Msg 8976, Level 16, State 1, Line 1
    Table error: Object ID 1042102753, index ID 1, partition ID 72057594064207872, alloc unit ID 72057594115194880 (type In-row data). Page (6:5704559) was not seen in the scan although its parent (6:5704811) and previous (6:5704558) refer to it. Check any previous errors.
    Msg 8978, Level 16, State 1, Line 1
    Table error: Object ID 1042102753, index ID 1, partition ID 72057594064207872, alloc unit ID 72057594115194880 (type In-row data). Page (6:5704560) is missing a reference from previous page (6:5704559). Possible chain linkage problem.
    There are 9657933 rows in 568116 pages for object "BI.FT_Equity_Holding".
    CHECKDB found 0 allocation errors and 8 consistency errors in table 'BI.FT_Equity_Holding' (object ID 1042102753).


    Service Broker Msg 9605, State 1: Conversation Priorities analyzed: 0.
    Msg 8909, Level 16, State 1, Line 1
    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 314379505500160 (type Unknown), page ID (6:5704546) contains an incorrect page ID in its page header. The PageId in the page header = (0:18).
    Msg 8909, Level 16, State 1, Line 1
    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 562949953355776 (type Unknown), page ID (6:5704559) contains an incorrect page ID in its page header. The PageId in the page header = (512:2).
    Msg 8909, Level 16, State 1, Line 1
    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 2449958382143799296 (type Unknown), page ID (6:5704547) contains an incorrect page ID in its page header. The PageId in the page header = (1:129053).
    CHECKDB found 0 allocation errors and 3 consistency errors not associated with any single object.

    Monday, July 01, 2013 5:55 AM