Home > Developer > SQL Server

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
Developer on Alibaba Coud: Build your first app with APIs, SDKs, and tutorials on the Alibaba Cloud. Read more ＞

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?
  2. Msg 8909, Level 16, State 1, line 1th
  4. 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.
  6. The error has been fixed.
  8. Msg 8909, Level 16, State 1, line 1th
  10. 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.
  12. The error has been fixed.
  14. Msg 8909, Level 16, State 1, line 1th
  16. 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.
  18. The error has been fixed.
  20. Msg 8909, Level 16, State 1, line 1th
  22. 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.
  24. The error has been fixed.
  26. Msg 8909, Level 16, State 1, line 1th
  28. 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.
  30. The error has been fixed.
  32. Msg 8909, Level 16, State 1, line 1th
  34. 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.
  36. The error has been fixed.
  38. Msg 8909, Level 16, State 1, line 1th
  40. 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.
  42. The error has been fixed.
  44. Msg 8909, Level 16, State 1, line 1th
  46. 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.
  48. The error has been fixed.
  50. CHECKDB found that there are 0 allocation errors and 8 consistency errors that are not associated with any single object.
  52. CHECKDB fixes 0 Allocation errors and 8 consistency errors that are not associated with any single object.
  54. FIX: Page (1:1772) was released from Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data).
  56. FIX: Page (1:1773) was released from Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data).
  58. FIX: Page (1:1774) was released from Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data).
  60. FIX: Page (1:1775) was released from Object ID 1694629080, index ID 0, partition ID 111059211386880, allocation unit ID 111059211386880 (type in-row data).
  62. FIX: the object ' dbo ' is already in the database ' Sssss ' .  Mycargooutrecord, Ix_mycargooutrecord_1 ' succeeded in regenerating the nonclustered index.
  64. FIX: the object ' dbo ' is already in the database ' Sssss ' .  Mycargooutrecord, Ix_mycargooutrecord ' succeeded in regenerating the nonclustered index.
  66. Msg 8928, Level 16, State 1, line 1th
  68. 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.
  70. The error has been fixed.
  72. Msg 8928, Level 16, State 1, line 1th
  74. 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.
  76. The error has been fixed.
  78. Msg 8928, Level 16, State 1, line 1th
  80. 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.
  82. The error has been fixed.
  84. Msg 8928, Level 16, State 1, line 1th
  86. 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.
  88. The error has been fixed.
  90. Msg 8945, Level 16, State 1, line 1th
  92. Table error: Object ID 1694629080 will be regenerated, index ID 2.
  94. The error has been fixed.
  96. Msg 8945, Level 16, State 1, line 1th
  98. Table error: Object ID 1694629080 will be regenerated, index ID 3.
  100. The error has been fixed.
  102. CHECKDB found 0 allocation errors and 4 conformance errors in table ' Mycargooutrecord ' (Object ID 1694629080).
  104. CHECKDB fixed 0 allocation errors and 4 conformance errors in table ' Mycargooutrecord ' (Object ID 1694629080).
  106. FIX: Page (1:1748) was released from Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data).
  108. FIX: Page (1:1749) was released from Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data).
  110. FIX: Page (1:1750) was released from Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data).
  112. FIX: Page (1:1751) was released from Object ID 2014630220, index ID 0, partition ID 132030806097920, allocation unit ID 132030806097920 (type in-row data).
  114. FIX: the object ' dbo ' is already in the database ' Sssss ' .  Myrecordmemory, Ix_myrecordmemory_1 ' succeeded in regenerating the nonclustered index.
  116. FIX: the object ' dbo ' is already in the database ' Sssss ' .  Myrecordmemory, Ix_myrecordmemory ' succeeded in regenerating the nonclustered index.
  118. Msg 8928, Level 16, State 1, line 1th
  120. 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.
  122. The error has been fixed.
  124. Msg 8928, Level 16, State 1, line 1th
  126. 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.
  128. The error has been fixed.
  130. Msg 8928, Level 16, State 1, line 1th
  132. 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.
  134. The error has been fixed.
  136. Msg 8928, Level 16, State 1, line 1th
  138. 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.
  140. The error has been fixed.
  142. Msg 8945, Level 16, State 1, line 1th
  144. Table error: Object ID 2014630220 will be regenerated, index ID 2.
  146. The error has been fixed.
  148. Msg 8945, Level 16, State 1, line 1th
  150. Table error: Object ID 2014630220 will be regenerated, index ID 3.
  152. The error has been fixed.
  154. CHECKDB found 0 allocation errors and 4 conformance errors in table ' Myrecordmemory ' (Object ID 2014630220).
  156. CHECKDB fixed 0 allocation errors and 4 conformance errors in table ' Myrecordmemory ' (Object ID 2014630220).
  158. CHECKDB found 0 allocation errors and 16 conformance errors in database ' Sssss '.
  160. 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

This article is an English version of an article which is originally in the Chinese language on aliyun.com and is provided for information purposes only. This website makes no representation or warranty of any kind, either expressed or implied, as to the accuracy, completeness ownership or reliability of the article or any translations thereof. If you have any concerns or complaints relating to the article, please send an email, providing a detailed description of the concern or complaint, to info-contact@alibabacloud.com. A staff member will contact you within 5 working days. Once verified, infringing content will be removed immediately.

Related Keywords:
incorrect syntax near in sql server 2008 sql ser sqlstate hy000 sql server error 0 sql error 2003 in statement 0 sql error code 0 sql server true false 0 1 microsoft sql server 7 0 download
Related Article
SQL Server R2 download address and serial number, available t...
Python reads the configuration file and connects to the datab...
pymssql calling SQL Server stored procedure with output param...
Where is SQL Server Configuration Manager in Windows10?
Nolock, HOLDLOCK, UPDLOCK, TABLOCK, Tablockx in SQL Server

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.

What's Trending
Top 10 Tags
datastax versions naming convention zookeeper client class definition md5 microsoft sql server 2005 data structures exception handling error handling
Top 10 Keywords
microsoft download center down wordpress address url site address url wordpress address url windows installer 4 0 download 302 not found web address url definition site address url wordpress db2 integer mac os installation step by step pdf abbreviation for return

A Free Trial That Lets You Build Big!

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

Get Started for Free

  • Sales Support

    1 on 1 presale consultation

    Chat Contact Sales

  • After-Sales Support

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

    Open a Ticket

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

    Learn More