SQL Server detected that the consistency-based logical I/O error PageID is incorrect (should be 1:1772, but actually 0:0). In file ' D:\Program Files\Microsoft SQL Ser

Source: Internet
Author: User
Tags sql server books server error log

SQL Server detected that the consistency-based logical I/O error PageID is incorrect (should be 1:1772, but actually 0:0). In the file ' D:\Program Files\Microsoft SQL SERVER\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\SGDTCC. This error occurs during the reading of the page (1:1772) in database ID 10, where the offset is 0x00000000dd8000 in MDF '. Additional messages in the SQL Server error log or the system event log may provide more detailed information. This is a serious error condition that threatens the integrity of the database and must be corrected immediately. Please perform a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; For more information, see SQL Server Books Online.

Prompt for errors when querying a table in the database

The fix code will take about 7 minutes, depending on your situation.

Sssss is the name of the data.

[SQL]View Plaincopy print?
    1. Use Sssss
    2. Go
    3. ALTER DATABASE sssss SET single_user
    4. Go
    5. DBCC CHECKDB (' sssss ', repair_allow_data_loss) with no_infomsgs
    6. Go
    7. ALTER DATABASE sssss SET multi_user
    8. Go
Use Sssssgoalter DATABASE sssss SET single_usergodbcc CHECKDB (' sssss ', repair_allow_data_loss) with No_infomsgsgoalter D Atabase sssss SET Multi_usergo

It's a bit long after 6:22. The repair results are as follows

[SQL]View Plaincopy print?
  1. Msg 8909, Level 16, State 1, line 1th
  2. Table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1748) contains the wrong page ID in its page header. PageId = (0:0) in the page header.
  3. The error has been fixed.
  4. Msg 8909, Level 16, State 1, line 1th
  5. Table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1749) contains the wrong page ID in its page header. PageId = (0:0) in the page header.
  6. The error has been fixed.
  7. Msg 8909, Level 16, State 1, line 1th
  8. Table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1750) contains the wrong page ID in its page header. PageId = (0:0) in the page header.
  9. The error has been fixed.
  10. Msg 8909, Level 16, State 1, line 1th
  11. Table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1751) contains the wrong page ID in its page header. PageId = (0:0) in the page header.
  12. The error has been fixed.
  13. Msg 8909, Level 16, State 1, line 1th
  14. Table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1772) contains the wrong page ID in its page header. PageId = (0:0) in the page header.
  15. The error has been fixed.
  16. Msg 8909, Level 16, State 1, line 1th
  17. Table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1773) contains the wrong page ID in its page header. PageId = (0:0) in the page header.
  18. The error has been fixed.
  19. Msg 8909, Level 16, State 1, line 1th
  20. Table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1774) contains the wrong page ID in its page header. PageId = (0:0) in the page header.
  21. The error has been fixed.
  22. Msg 8909, Level 16, State 1, line 1th
  23. Table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1775) contains the wrong page ID in its page header. PageId = (0:0) in the page header.
  24. The error has been fixed.
  25. CHECKDB found that there are 0 allocation errors and 8 consistency errors that are not associated with any single object.
  26. CHECKDB fixes 0 Allocation errors and 8 consistency errors that are not associated with any single object.
  27. FIX: Page (1:1772) was released from Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data).
  28. FIX: Page (1:1773) was released from Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data).
  29. FIX: Page (1:1774) was released from Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data).
  30. FIX: Page (1:1775) was released from Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data).
  31. FIX: the object ' dbo ' is already in the database ' Sssss ' .  Mycargooutrecord, Ix_mycargooutrecord_1 ' succeeded in regenerating the nonclustered index.
  32. FIX: the object ' dbo ' is already in the database ' Sssss ' .  Mycargooutrecord, Ix_mycargooutrecord ' succeeded in regenerating the nonclustered index.
  33. Msg 8928, Level 16, State 1, line 1th
  34. Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data): Unable to Process page (1:1772).  For more information, see additional error messages.
  35. The error has been fixed.
  36. Msg 8928, Level 16, State 1, line 1th
  37. Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data): Unable to Process page (1:1773).  For more information, see additional error messages.
  38. The error has been fixed.
  39. Msg 8928, Level 16, State 1, line 1th
  40. Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data): Unable to Process page (1:1774).  For more information, see additional error messages.
  41. The error has been fixed.
  42. Msg 8928, Level 16, State 1, line 1th
  43. Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data): Unable to Process page (1:1775).  For more information, see additional error messages.
  44. The error has been fixed.
  45. Msg 8945, Level 16, State 1, line 1th
  46. Table error: Object ID 1694629080 will be regenerated, index ID 2.
  47. The error has been fixed.
  48. Msg 8945, Level 16, State 1, line 1th
  49. Table error: Object ID 1694629080 will be regenerated, index ID 3.
  50. The error has been fixed.
  51. CHECKDB found 0 allocation errors and 4 conformance errors in table ' Mycargooutrecord ' (Object ID 1694629080).
  52. CHECKDB fixed 0 allocation errors and 4 conformance errors in table ' Mycargooutrecord ' (Object ID 1694629080).
  53. FIX: Page (1:1748) was released from Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data).
  54. FIX: Page (1:1749) was released from Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data).
  55. FIX: Page (1:1750) was released from Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data).
  56. FIX: Page (1:1751) was released from Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data).
  57. FIX: the object ' dbo ' is already in the database ' Sssss ' .  Myrecordmemory, Ix_myrecordmemory_1 ' succeeded in regenerating the nonclustered index.
  58. FIX: the object ' dbo ' is already in the database ' Sssss ' .  Myrecordmemory, Ix_myrecordmemory ' succeeded in regenerating the nonclustered index.
  59. Msg 8928, Level 16, State 1, line 1th
  60. Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data): Unable to Process page (1:1748).  For more information, see additional error messages.
  61. The error has been fixed.
  62. Msg 8928, Level 16, State 1, line 1th
  63. Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data): Unable to Process page (1:1749).  For more information, see additional error messages.
  64. The error has been fixed.
  65. Msg 8928, Level 16, State 1, line 1th
  66. Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data): Unable to Process page (1:1750).  For more information, see additional error messages.
  67. The error has been fixed.
  68. Msg 8928, Level 16, State 1, line 1th
  69. Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data): Unable to Process page (1:1751).  For more information, see additional error messages.
  70. The error has been fixed.
  71. Msg 8945, Level 16, State 1, line 1th
  72. Table error: Object ID 2014630220 will be regenerated, index ID 2.
  73. The error has been fixed.
  74. Msg 8945, Level 16, State 1, line 1th
  75. Table error: Object ID 2014630220 will be regenerated, index ID 3.
  76. The error has been fixed.
  77. CHECKDB found 0 allocation errors and 4 conformance errors in table ' Myrecordmemory ' (Object ID 2014630220).
  78. CHECKDB fixed 0 allocation errors and 4 conformance errors in table ' Myrecordmemory ' (Object ID 2014630220).
  79. CHECKDB found 0 allocation errors and 16 conformance errors in database ' Sssss '.
  80. checkdb  fixed  0  allocation errors and  16  conformance errors in database  
Msg 8909, Level 16, State 1, 1th row table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1748) contains the wrong page ID in its page header.        PageId = (0:0) in the page header. The error has been fixed. Msg 8909, Level 16, State 1, 1th row table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1749) contains the wrong page ID in its page header.        PageId = (0:0) in the page header. The error has been fixed. Msg 8909, Level 16, State 1, 1th row table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1750) contains the wrong page ID in its page header.        PageId = (0:0) in the page header. The error has been fixed. Msg 8909, Level 16, State 1, 1th row table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1751) contains the wrong page ID in its page header.        PageId = (0:0) in the page header. The error has been fixed. Msg 8909, Level 16, State 1, 1th row table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1772) contains the wrong page ID in its page header.        PageId = (0:0) in the page header. The error has been fixed. Msg 8909, Level 16, State 1, 1th row table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1773) contains the wrong page ID in its page header.        PageId = (0:0) in the page header. The error has been fixed. Msg 8909, Level 16, State 1, 1th row table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1774) contains the wrong page ID in its page header.        PageId = (0:0) in the page header. The error has been fixed. MSG 8909, Level 16, State 1, 1th row table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 0 (type Unknown), page ID (1:1775) contains the wrong page ID in its page header.        PageId = (0:0) in the page header. The error has been fixed. CHECKDB found that there are 0 allocation errors and 8 consistency errors that are not associated with any single object. CHECKDB fixes 0 Allocation errors and 8 consistency errors that are not associated with any single object. FIX: Page (1:1772) was released from Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data). FIX: Page (1:1773) was released from Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data). FIX: Page (1:1774) was released from Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data). FIX: Page (1:1775) was released from Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data). FIX: The object ' dbo ' is already in the database ' Sssss '. Mycargooutrecord, Ix_mycargooutrecord_1 ' succeeded in regenerating the nonclustered index. FIX: The object ' dbo ' is already in the database ' Sssss '. Mycargooutrecord, Ix_mycargooutrecord ' succeeded in regenerating the nonclustered index. Msg 8928, Level 16, State 1, line 1th object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type In-row data): Unable to process page (1 : 1772).        For more information, see additional error messages. The errorhas been fixed. Msg 8928, Level 16, State 1, line 1th object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type In-row data): Unable to process page (1 : 1773).        For more information, see additional error messages. The error has been fixed. Msg 8928, Level 16, State 1, line 1th object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type In-row data): Unable to process page (1 : 1774).        For more information, see additional error messages. The error has been fixed. Msg 8928, Level 16, State 1, line 1th object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type In-row data): Unable to process page (1 : 1775).        For more information, see additional error messages. The error has been fixed.        Msg 8945, Level 16, State 1, Row 1th table error: Object ID 1694629080 will be regenerated, index ID 2. The error has been fixed.        Msg 8945, Level 16, State 1, Row 1th table error: Object ID 1694629080 will be regenerated, index ID 3. The error has been fixed. CHECKDB found 0 allocation errors and 4 conformance errors in table ' Mycargooutrecord ' (Object ID 1694629080). CHECKDB fixed 0 allocation errors and 4 conformance errors in table ' Mycargooutrecord ' (Object ID 1694629080). FIX: Page (1:1748) was released from Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data). FIX: Page (1:1749) was released from Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data). FIX: Page (1: 1750) Released from Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data). FIX: Page (1:1751) was released from Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data). FIX: The object ' dbo ' is already in the database ' Sssss '. Myrecordmemory, Ix_myrecordmemory_1 ' succeeded in regenerating the nonclustered index. FIX: The object ' dbo ' is already in the database ' Sssss '. Myrecordmemory, Ix_myrecordmemory ' succeeded in regenerating the nonclustered index. Msg 8928, Level 16, State 1, line 1th object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type In-row data): Unable to process page (1 : 1748).        For more information, see additional error messages. The error has been fixed. Msg 8928, Level 16, State 1, line 1th object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type In-row data): Unable to process page (1 : 1749).        For more information, see additional error messages. The error has been fixed. Msg 8928, Level 16, State 1, line 1th object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type In-row data): Unable to process page (1 : 1750).        For more information, see additional error messages. The error has been fixed. Msg 8928, Level 16, State 1, line 1th object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type In-row data): Unable to process page (1 : 1751). AboutFor more information, see additional error messages. The error has been fixed.        Msg 8945, Level 16, State 1, Row 1th table error: Object ID 2014630220 will be regenerated, index ID 2. The error has been fixed.        Msg 8945, Level 16, State 1, Row 1th table error: Object ID 2014630220 will be regenerated, index ID 3. The error has been fixed. CHECKDB found 0 allocation errors and 4 conformance errors in table ' Myrecordmemory ' (Object ID 2014630220). CHECKDB fixed 0 allocation errors and 4 conformance errors in table ' Myrecordmemory ' (Object ID 2014630220). CHECKDB found 0 allocation errors and 16 conformance errors in database ' Sssss '. CHECKDB fixed 0 Allocation errors and 16 consistency errors in database ' Sssss '.

It is normal to query the table after the repair is complete.

SQL Server detected that the consistency-based logical I/O error PageID is incorrect (should be 1:1772, but actually 0:0). In file ' D:\Program Files\Microsoft SQL Ser

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.