April 5, 2010 at 7:54 pm
Any ideas, please!
April 6, 2010 at 1:12 am
If you're referring to the checkDB errors that you posted on the 13th Feb then, as I posted multiple times, the errors are not repairable in any way. The damage is to the system tables, CheckDB does not repair them.
Allow updates does not work on SQL 2005, attempting to run the delete statements that you have will return an error.
Msg 259, Level 16, State 1, Line 5
Ad hoc updates to system catalogs are not allowed.
In addition, sys.partitions is a view, not a table.
Furthermore, I'm really curious why you're trying to delete two partitions (do you know what's in them?) when your problem is a missing page reference in an index chain.
If you mess with the 2005 system tables without fully understanding what you're doing, you can completely wreck the database beyond all use. If you absolutely must, test this out on a copy of the database, not on the original
You have two options.
Restore from a clean backup. If you're missing data once you've restored, it's because you haven't restored all the log backups right up til the end (note that you cannot skip log backups)
Script out all the objects from the damaged database(some may fail), script all the data, some might fail and recreate the database.
p.s. Why run checkAlloc twice? If the first run fails, the second will fail too, if the first run
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 15, 2012 at 10:26 pm
failed with the following error: "Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 8800782319616 (type Unknown), page (40498:1). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -1.
Object ID 510624862, index ID 1, partition ID 72057594053066752, alloc unit ID 72057594056146944 (type In-row data): Page (1:110858) could not be processed. See other errors for details.
Table error: Object ID 510624862, index ID 1, partition ID 72057594053066752, alloc unit ID 72057594056146944 (type In-row data). Page (1:110858) was not seen in the scan although its parent (1:42595) and previous (1:110857) refer to it. Check any previous errors.
Table error: Object ID 510624862, index ID 1, partition ID 72057594053066752, alloc unit ID 72057594056146944 (type In-row data). Page (1:110859) is missing a reference from previous page (1:110858). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'HIST_STAT3' (object ID 510624862).
CHECKDB found 0 allocation errors and 4 consistency errors in database 'Prod.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
====================
Can you please let me know DB restore is last options or i can run REPAIRE_ALLLOW_DATA_LOSS for solving the issues
May 15, 2012 at 11:47 pm
Please post new questions in a new thread. thank you
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply