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.
Author |
Topic |
francisb
Starting Member
7 Posts |
Posted - 2009-12-03 : 20:52:07
|
Hi,Can anyone help me fix this?This is on a SQL 6.5 production server running an ERP software. The customer noticed the corruption about 5 days after it occured. Going back to a backup is nearly impossible. It is crucial that I manage to repair that database for them... DBCC commands I ran so far point to corruption of a single table (batchctl) which contains about 232,000 records. Unfortunately, it is not an index, but a data table and I can't just drop it. I've included the output of the DBCC commands below. CHECKDB and CHECKTABLE actually returned a much larger number of messages, all saying "Keys in data page should be in ascending order" with a different page number. I've only listed the last two entries here, but I have all the details if needed.I've been through something similar with a Microsoft SQL Engineer a few years ago. I know they have 'undocumented' procedures that allow them to re-link pages, etc. The only problem is Microsoft won't open a support call because 6.5 is outdated (I tried calling them and they suggested to try this forum).Any kind soul out there capable of helping with this issue? All suggestions welcome.Thanks a lot!~ F. -- DBCC CHECKDB --Msg 2511, Level 16, State 1, Server SERVEUR_HVF, Line 5Table Corrupt: Keys in data page should be in ascending order; checkpage number 2229733Msg 2503, Level 16, State 1, Server SERVEUR_HVF, Line 5Table Corrupt: Page linkage is not consistent; check the followingpages: (current page#=2229737; page# pointing to this page=2229733;previous page# indicated in this page=2229735)-- DBCC CHECKTABLE --Msg 2511, Level 16, State 1, Server SERVEUR_HVF, Line 5Table Corrupt: Keys in data page should be in ascending order; checkpage number 2229733Msg 2503, Level 16, State 1, Server SERVEUR_HVF, Line 5Table Corrupt: Page linkage is not consistent; check the followingpages: (current page#=2229737; page# pointing to this page=2229733;previous page# indicated in this page=2229735)-- DBCC CHECKALLOC --Msg 2529, Level 16, State 7, Server SERVEUR_HVF, Line 5Table Corrupt: Page 766234 not found-- DBCC NEWALLOC --***************************************************************TABLE: batchctl OBJID = 528004912INDID=1 FIRST=2100216 ROOT=2107899 DPAGES=35440 SORT=1Msg 2502, Level 16, State 1, Server SERVEUR_HVF, Line 5Table Corrupt: A page is linked in more than one chain; check thispage:page number=2229737 allocation status=118 Data level: 1. 0 Data Pages in 4449 extents.INDID=2 FIRST=1639432 ROOT=1638402 DPAGES=3106 SORT=0INDID=3 FIRST=1850784 ROOT=1848804 DPAGES=3842 SORT=0TOTAL # of extents = 4449*************************************************************** |
|
|
|
|
|
|