Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 A little direction ...

Author  Topic 

ETL_DBA
Starting Member

2 Posts

Posted - 2012-04-02 : 13:40:32
Like some others that have posted here, I've been thrown into the fire to solve a situation picking up where someone else left off ... so here goes ...

Ran DBCC on our main database and this is the output I receive:
[To my untrained eye, it's not huge but still a problem to tend to just the same]
-----------------
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 2, index ID 255, page ID (1:478741). The PageId in the page header = (1:478749).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 2, index ID 255, page ID (1:478742). The PageId in the page header = (1:478750).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 2, index ID 255, page ID (1:478743). The PageId in the page header = (1:478751).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1680594367, index ID 0: Page (1:478740) could not be processed. See other errors for details.
Server: Msg 8941, Level 16, State 1, Line 1
Table error: Object ID 1680594367, index ID 0, page (1:478740). Test (sorted [i].offset >= PAGEHEADSIZE) failed. Slot 7, offset 0x1 is invalid.
Server: Msg 8942, Level 16, State 1, Line 1
Table error: Object ID 1680594367, index ID 0, page (1:478740). Test (sorted[i].offset >= max) failed. Slot 0, offset 0x7 overlaps with the prior row.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1680594367, index ID 0: Page (1:478741) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1680594367, index ID 0: Page (1:478742) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1680594367, index ID 0: Page (1:478743) could not be processed. See other errors for details.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'sysindexes' (object ID 2).
CHECKDB found 0 allocation errors and 6 consistency errors in table 'tmp_anal_grp_mthds_bak' (object ID 1680594367).
CHECKDB found 0 allocation errors and 9 consistency errors in database 'Newburgh'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Newburgh ).
----------------------------

Just looking for a little direction. Since I'm seeing the name of a tmp table I'm leaning towards a repair but I need to do "due diligence" and see if I can see what the data actually is.

Thanks.

Kevin

ETL_DBA
Starting Member

2 Posts

Posted - 2012-04-02 : 14:05:03
This is SQL 2000, by the way ....
Go to Top of Page

prett
Posting Yak Master

212 Posts

Posted - 2012-04-12 : 02:12:44
I found this Microsoft Kb article article on this error:

http://support.microsoft.com/kb/308795

One more article: http://recoverdatabase.blogspot.in/2011/09/how-to-resolve-error-msg-823-level-24.html
Go to Top of Page

elliswhite
Starting Member

36 Posts

Posted - 2014-05-10 : 04:13:29
You need to restore SQL database from ful backup if the full backup is not available then try any entrusted SQL recovery tool.
Go to Top of Page
   

- Advertisement -