June 23, 2009 at 11:09 pm
Msg 7985, Level 16, State 2, Line 1
System table pre-checks: Object ID 5. Could not read and latch page (1:43844) with latch type SH. Check statement terminated due to unrepairable error.
DBCC results for 'UserDataBaseLD'.
Msg 5233, Level 16, State 98, Line 1
Table error: alloc unit ID 327680, page (1:43844). The test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. The values are 29493513 and -1.
CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 1 consistency errors in database 'UserDataBasLD'.
Please Help how to resolve this issue.
June 23, 2009 at 11:23 pm
Do you have backups? I think you might need to restore the database from recent backup.
See Paul Randal's blog below
http://www.sqlskills.com/blogs/paul/post/CHECKDB-From-Every-Angle-Can-CHECKDB-repair-everything.aspx
Edit: added Paul's link
June 23, 2009 at 11:29 pm
i restored from the latest backup and got the same error message when i tried the DBCC checkDB.
the Object that is given in the error message is "sysrowsets" which is a system table.
June 24, 2009 at 12:43 am
Do you have an earlier backup that is usable?
You've got an irreparable error there. There is no way to fix that. You have only two options. Restore a clean backup or recreate the database. If you have no clean backup then you need to script all the objects (tables, views, procedures, triggers, etc), then bcp all of the data out. There's a good chance that not all of the tables will export because of the corruption. Once you've got everything that you can out, create a new database, load all of the objects, import all of the data, drop the old DB.
Take a look at this article. http://www.sqlservercentral.com/articles/65804/. There's a section towards the end on irreparable corruption.
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 - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply