SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 New to SQL Server Programming
 databases is giving this error
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

ussanjeewa
Starting Member

Sri Lanka
1 Posts

Posted - 10/04/2012 :  09:17:58  Show Profile  Reply with Quote
One of our databases is giving this error

Msg 8929, Level 16, State 1, Line 1
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data): Errors found in off-row data with ID 1082130432 owned by data record identified by RID = (1:415:1)
Msg 8929, Level 16, State 1, Line 1
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data): Errors found in off-row data with ID 1082130432 owned by data record identified by RID = (1:632:0)
Msg 8914, Level 16, State 1, Line 1
Incorrect PFS free space information for page (1:9780) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 80_PCT_FULL, actual value 100_PCT_FULL.
Msg 8961, Level 16, State 2, Line 1
Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). The off-row data node at page (1:9780), slot 1, text ID 1082130432 does not match its reference from page (1:415), slot 1.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'sys.sysobjvalues' (object ID 60).
CHECKDB found 0 allocation errors and 4 consistency errors in database 'TBS_Master'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (MYDB).

chadmat
The Chadinator

USA
1974 Posts

Posted - 10/04/2012 :  13:14:41  Show Profile  Visit chadmat's Homepage  Reply with Quote
If you have a backup, you can either restore from backup, or try to retrieve the corrupt pages/data. You could also try to run a dbcc checkdb with repair, but will likely lose data.

-Chad
Go to Top of Page

NehwalSaina
Starting Member

India
2 Posts

Posted - 10/08/2012 :  07:04:38  Show Profile  Reply with Quote
Repairing corrupt and damaged SQL Server database has never been so easy before. For excellent and accurate database recovery, use <unspammed> that is not only easy to use but its interactive and user-friendly screens makes this tool a favorite among novice computer users as well. It is the most effective tool to deal with any corruption issues and retrieve MDF files along with their inaccessible data.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.08 seconds. Powered By: Snitz Forums 2000