March 19, 2015 at 10:52 am
I started geting this error last night on 1 of our SQL servers when running a few different processes. 1 is a very long stored procedure called from a web site app. Another is a very simple stored procedure writing a record to MySQL through a linked server.
All was fine earlier yesterday.
I rebooted.
Select @@VERSION = Microsoft SQL Server 2005 - 9.00.5069.00 (X64) Aug 22 2012 18:02:46 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
I ran CHECKDB on the main database with these results. The table listed below are not used by the failing processes. (I have never even used them)
Ideas ???
Msg 2508, Level 16, State 1, Line 1
The In-row data USED page count for object "mp_checkout", index ID 2, partition ID 568297135865856, alloc unit ID 568297135865856 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.
Msg 2508, Level 16, State 3, Line 1
The In-row data RSVD page count for object "mp_checkout", index ID 2, partition ID 568297135865856, alloc unit ID 568297135865856 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'mp_checkout' (object ID 81591529).
Msg 2508, Level 16, State 1, Line 1
The In-row data USED page count for object "SearchEx_drop", index ID 11, partition ID 3178664293761024, alloc unit ID 3178664293761024 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.
Msg 2508, Level 16, State 3, Line 1
The In-row data RSVD page count for object "SearchEx_drop", index ID 11, partition ID 3178664293761024, alloc unit ID 3178664293761024 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.
Msg 2508, Level 16, State 1, Line 1
The In-row data USED page count for object "SearchEx_drop", index ID 17, partition ID 4867514154024960, alloc unit ID 4867514154024960 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.
Msg 2508, Level 16, State 3, Line 1
The In-row data RSVD page count for object "SearchEx_drop", index ID 17, partition ID 4867514154024960, alloc unit ID 4867514154024960 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.
Msg 2508, Level 16, State 1, Line 1
The In-row data USED page count for object "SearchEx_drop", index ID 18, partition ID 5148989130735616, alloc unit ID 5148989130735616 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.
Msg 2508, Level 16, State 3, Line 1
The In-row data RSVD page count for object "SearchEx_drop", index ID 18, partition ID 5148989130735616, alloc unit ID 5148989130735616 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.
CHECKDB found 0 allocation errors and 6 consistency errors in table 'SearchEx_drop' (object ID 1257927703).
Msg 2508, Level 16, State 1, Line 1
The In-row data USED page count for object "SearchExDisplay_drop", index ID 2, partition ID 646438083100672, alloc unit ID 646438083100672 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.
Msg 2508, Level 16, State 3, Line 1
The In-row data RSVD page count for object "SearchExDisplay_drop", index ID 2, partition ID 646438083100672, alloc unit ID 646438083100672 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'SearchExDisplay_drop' (object ID 1273927760).
CHECKDB found 0 allocation errors and 10 consistency errors in database 'MyDatabase'.
I ran DBCC UPDATEUSAGE on those tables & rebooted again.
March 19, 2015 at 10:58 pm
Do you have torn page or checksum detection turned on the database? If so check msdb.dbo.suspect_pages to see if there have been any IO issues.
How often do you checkdb? When was the last successful one?
March 20, 2015 at 6:48 am
TORN PAGE is on.
Select * from msdb.dbo.suspect_pages gives 0 results
I have not run CHECKDB for a long time, until the results posted above.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply