August 29, 2007 at 10:01 am
Hi all, i hope you can help here.
I am seeing a number of issues when running DBCC command against a DB of ours, the upshot is the following error messages, could someone help in deciphering the results please, and I have very little knowledge in this area.
DBCC CHECKDB WITH
PHYSICAL_ONLY
==================SAMPLE ERROR==========================
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -2061565952, index ID 42, page ID (1:1415800). The PageId in the page header = (256:475185).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -2061549542, index ID 44, page ID (1:1415801). The PageId in the page header = (256:475204).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -1945590825, index ID 0, page ID (1:747735). The PageId in the page header = (32768:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -1795686400, index ID 8249, page ID (1:1466909). The PageId in the page header = (565:808399920).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -1777795072, index ID 8241, page ID (1:1466962). The PageId in the page header = (2869:808399920).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -1374404552, index ID 8, page ID (1:1415819). The PageId in the page header = (256:475232).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -1202585600, index ID 1, page ID (1:1415813). The PageId in the page header = (256:475128).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -2061565952)' (object ID -2061565952).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -2061549542)' (object ID -2061549542).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1945590825)' (object ID -1945590825).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1795686400)' (object ID -1795686400).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1777795072)' (object ID -1777795072).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1374404552)' (object ID -1374404552).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1202585600)' (object ID -1202585600).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -1202569202, index ID 49, page ID (1:1415795). The PageId in the page header = (256:475189).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -1202569180, index ID 38, page ID (1:1415831). The PageId in the page header = (256:475223).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -858963932, index ID 22, page ID (1:1415824). The PageId in the page header = (256:475212).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -687194058, index ID 14, page ID (1:1415789). The PageId in the page header = (256:475242).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -343605248, index ID 17, page ID (1:1415837). The PageId in the page header = (256:475123).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:747728). The PageId in the page header = (312:20381986).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:2077655). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:2077666). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:2077667). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 8224, page ID (1:2077679). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 12576, page ID (1:1466885). The PageId in the page header = (12083:805306624).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1202569202)' (object ID -1202569202).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1202569180)' (object ID -1202569180).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -858963932)' (object ID -858963932).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -687194058)' (object ID -687194058).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -343605248)' (object ID -343605248).
DBCC results for 'PSE_PRE_REINDEX'.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 12576, page ID (1:1466908). The PageId in the page header = (12083:805306624).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 14368, page ID (1:1466927). The PageId in the page header = (12083:805306624).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 14368, page ID (1:1466932). The PageId in the page header = (12084:805306624).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 14368, page ID (1:1466945). The PageId in the page header = (12083:805306624).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 271, index ID 30319, page ID (1:747740). The PageId in the page header = (8224:540422708).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 8224, index ID 8192, page ID (1:1466884). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 37697, index ID 8224, page ID (1:1466866). The PageId in the page header = (1:37697).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 37746, index ID 8224, page ID (1:1466944). The PageId in the page header = (1:37770).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 38172, index ID 8224, page ID (1:1466902). The PageId in the page header = (1:38193).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1466830, index ID 8243, page ID (1:1466867). The PageId in the page header = (14133:825373488).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 3153998, index ID 9217, page ID (1:1466879). The PageId in the page header = (14129:842215472).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 16777364, index ID 8224, page ID (1:1466939). The PageId in the page header = (8494:668720).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 16777366, index ID 8224, page ID (1:1466903). The PageId in the page header = (8980:800048).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 19005444, index ID 0, page ID (1:746896). The PageId in the page header = (25455:1277165881).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 20513061, index ID 0, page ID (1:747717). The PageId in the page header = (28492:1668899184).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 31457280, index ID 0, page ID (1:747716). The PageId in the page header = (303:19792173).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 67207168, index ID 0, page ID (1:746848). The PageId in the page header = (28673:1006713601).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 67207168, index ID 0, page ID (1:746855). The PageId in the page header = (28673:1006713601).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 67207168, index ID 0, page ID (1:746861). The PageId in the page header = (28673:1006713601).
CHECKDB found 0 allocation errors and 10 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 271)' (object ID 271).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 8224)' (object ID 8224).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 37697)' (object ID 37697).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 37746)' (object ID 37746).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 38172)' (object ID 38172).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 1466830)' (object ID 1466830).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 3153998)' (object ID 3153998).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 16777364)' (object ID 16777364).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 16777366)' (object ID 16777366).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 19005444)' (object ID 19005444).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 20513061)' (object ID 20513061).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 31457280)' (object ID 31457280).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 67207168, index ID 0, page ID (1:746878). The PageId in the page header = (28673:1006713601).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 67207168, index ID 0, page ID (1:746891). The PageId in the page header = (28673:1006713601).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 67207168, index ID 0, page ID (1:746897). The PageId in the page header = (28673:1006713601).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 88736881, index ID 0: Page (1:1519405) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 88736881, index ID 0, page (1:1519405), row 0. Test (columnOffsets->offTbl [varColumnNumber] <= (nextRec - pRec)) failed. Values are 2874 and 2864.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 88736881, index ID 0, page ID (1:1519406). The PageId in the page header = (1:1519412).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 88736881, index ID 0: Page (1:1519406) could not be processed. See other errors for details.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 88736881, index ID 0, page ID (1:1519407). The PageId in the page header = (1:1519413).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 88736881, index ID 0: Page (1:1519407) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 88736881, index ID 0: Page (1:1519411) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 88736881, index ID 0, page (1:1519411), row 1. Test (columnOffsets->offTbl [varColumnNumber] <= (nextRec - pRec)) failed. Values are 2857 and 2848.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 88736881, index ID 0, page ID (1:1519412). The PageId in the page header = (1:1519420).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 88736881, index ID 0: Page (1:1519412) could not be processed. See other errors for details.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 88736881, index ID 0, page ID (1:1519413). The PageId in the page header = (1:1519421).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 88736881, index ID 0: Page (1:1519413) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 88736881, index ID 0: Page (1:1519419) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 88736881, index ID 0, page (1:1519419), row 0. Test (columnOffsets->offTbl [varColumnNumber] <= (nextRec - pRec)) failed. Values are 2864 and 2857.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 88736881, index ID 0, page ID (1:1519420). The PageId in the page header = (1:1519426).
==================ENd ERROR=============================
Cheers for any help, much appreciated.
August 29, 2007 at 10:29 am
http://msdn2.microsoft.com/en-us/library/aa275735(sql.80).aspx
There's links to the rest of the errors on the left-hand side.
Your best bet is to restore the database to a previous backup. If you don't have one, run the DBCC CHECKDB.
Note that there is a reported bug with this particular error and the DBCC CHECKDB command. Make sure you are on the latest service pack before running it.
August 30, 2007 at 1:35 am
Hi Pam, any help is much appreciated as I am no expert.
We do already have SP4 installed, so one would hope the bug had been ironed out in that.
We have tried a very old restore and that seemed fine, but this all happened when we added new, or should I say additional hardware, and we did not capture the error until really late on, so unless we can rectify this error, we stand to lose a lot of data, as non of the restores we have are clean.
I have already run DBCC CHECKDB with several different combinations and the enclosed was a result of one as I have said, not sure what else we could do if we cannot sort it out.
Cheers.
August 30, 2007 at 12:32 pm
As the errors indicate hardware failures, you probably have something wrong in the setup / hardware configuration.
Regardless, you really only have two options at this point to fix the database after you verify that there are no hardware issues:
1) Go back to your most recent working restore.
2) Run DBCC CHECKDB REPAIR_REBUILD and if that doesn't work, run DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS
August 30, 2007 at 3:43 pm
Thanks for your input.
August 30, 2007 at 6:12 pm
I just now noticed you did a physical only check. Try running a generic DBCC CHECKDB first if you can.
Good luck!
August 31, 2007 at 12:21 am
Will do, cheers
September 12, 2007 at 6:37 pm
Looks like you've got a controller issue - some of the pages have been wiped out with random garbage and one oset of pages has been overwritten by the next extent's pages. Definitely a hardware issues. If you don't have a backup there's no point running REPAIR_REBUILD - as the output from CHECKDB will have told you, REPAIR_ALLOW_DATA_LOSS is required to fix these. The fix is to delete the pages (and fixup any links). However, all this is doing is fixing the symptom of the problem - not the cause.
I just happened to have blogged about page checksums and SQLIOSim that you can use to determine for sure that the IO subsystem is to blame - see http://www.sqlskills.com/blogs/paul/2007/09/12/HowToTellIfTheIOSubsystemIsCausingCorruptions.aspx for more details.
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply