June 16, 2009 at 11:25 am
A customer using an application that I provide support for received a program generated error referring to "torn page". I got the database from the customer and restored it and ran a dbcc checkdb and got the following error from one of the tables:
DBCC results for 'FeedbackProperties'.
Msg 8928, Level 16, State 1, Line 1
Object ID 85575343, index ID 0, partition ID 5608265678848, alloc unit ID 5608265678848 (type In-row data): Page (1:151) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 85575343, index ID 0, partition ID 5608265678848, alloc unit ID 5608265678848 (type In-row data), page (1:151). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -1.
There are 7 rows in 1 pages for object "FeedbackProperties".
CHECKDB found 0 allocation errors and 2 consistency errors in table 'FeedbackProperties' (object ID 85575343).
What are my options if there is no backup prior to this error occuring?
June 16, 2009 at 11:44 am
Check Paul Randall's blog on sqlskills.com, microsoft blog and other places including this site. there must be something related there. May be he or Gail or other experts can help you in this when they arrive here.
June 16, 2009 at 11:54 am
Thanks. I'll check that out and check the post later.
Thanks
June 16, 2009 at 12:34 pm
That page has been corrupted (torn-page is usually from power-outage - did that happen?) and is not recoverable. You've got two choices - restore from a backup (possibly even a single-page restore) or run repair, which will delete the page and you'll lose data. You might decide to just drop that table if you're able to recreate it from other sources and bring it up-to-date with the rest of the database.
Hope this helps.
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
June 16, 2009 at 12:36 pm
Is that the entire output of CheckDB? If not, please run the following and post the full and complete output.
DBCC CHECKDB (< Database Name > ) WITH NO_INFOMSGS, ALL_ERRORMSGS
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
June 16, 2009 at 12:45 pm
Also, since you are on 2005 you should change the page verification to CHECKSUM (once you have this issue resolved).
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
June 17, 2009 at 6:16 am
Paul,
As far as the table replacement goes, can I delete that table and then import a blank version of it from a known good database?
Thanks
June 17, 2009 at 7:47 am
Yes, if that solution works for you.
You also need to investigate why this happened. Torn-page commonly happens when the server loses power and some component of the I/O subsystem fails to complete an in-progress write operation.
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