Errors that checkdb won''t repair.
-
Hi all.
I've got a database with some consistency and allocation errors and it seems that checkdb doesn't want to repair them. Here's the report from checkdb (it was run with repair_allow_data_loss)
Msg 2536, Sev 16: DBCC results for 'MainDB'. [SQLSTATE 01000]
Msg 1505, Sev 16: CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 1. Most significant primary key is 'Oct 17 2005 11:59PM'. [SQLSTATE 23000]
Msg 8968, Sev 16: Table error: IAM page (0:0) (object ID 1246627484, index ID 1) is out of the range of this database. [SQLSTATE 42000]
Msg 8979, Sev 16: Table error: Object ID 315148168, index ID 1. Page (1:12963862) is missing references from parent (unknown) and previous (page (1:12963861)) nodes. Possible bad root entry in sysindexes. [SQLSTATE 42000]
Msg 8977, Sev 16: Table error: Object ID 315148168, index ID 1. Parent node for page (1:12963863) was not encountered. [SQLSTATE 42000]
Msg 8922, Sev 16: Could not repair this error. [SQLSTATE 01000]
Msg 8924, Sev 16: Repairing this error requires other errors to be corrected first. [SQLSTATE 01000]
Msg 8981, Sev 16: Table error: Object ID 315148168, index ID 1. The next pointer of (1:12963863) refers to page (1:12963864). Neither (1:12963864) nor its parent were encountered. Possible bad chain linkage. [SQLSTATE 42000]
Msg 8906, Sev 16: Page (1:5052010) in database ID 13 is allocated in the SGAM (1:4601089) and PFS (1:5046912), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'. [SQLSTATE 42000]
Msg 8906, Sev 16: Page (1:5052012) in database ID 13 is allocated in the SGAM (1:4601089) and PFS (1:5046912), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'. [SQLSTATE 42000]
Msg 8924, Sev 16: Repairing this error requires other errors to be corrected first. [SQLSTATE 01000]
Msg 8990, Sev 16: CHECKDB found 0 allocation errors and 3 consistency errors in table 'BALANCEHistory' (object ID 315148168). [SQLSTATE 01000]
Msg 8922, Sev 16: Could not repair this error. [SQLSTATE 01000]
Msg 8924, Sev 16: Repairing this error requires other errors to be corrected first. [SQLSTATE 01000]
CHECKDB found 2 allocation errors and 0 consistency errors in table 'BALANCE' (object ID 1246627484). [SQLSTATE 01000]
CHECKDB found 2 allocation errors and 3 consistency errors in database 'MainDB'. [SQLSTATE 01000]
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (MainDB repair_allow_data_loss). [SQLSTATE 01000]
Thanks
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
This was removed by the editor as SPAM
-
I have had this problem recently myself. To resolve it I have done two things: rebuilt indexes an all the tables in affected database and, after that was completed, ran dbcc checkdb for as many time and with as many options ( with_data_loss or fast ) as I was asked to do. It took a while, but once done I was back in business.
-
Hi,
This is Minaz Amin.
Check this:
1.What is the SQL Server version?
2. Check the System event log and also SQL Server error log.
Steps :
1. Try to rubild all the indexes.
2. Run DBCC Checkdb with Repail_Rebuild
Do let me know.
Regards,
Minaz Amin
Email ID : meenakshikundar@yahoo.com
Ph:9341735900
"More Green More Oxygen !! Plant a tree today"
-
I had a question regarding the repair and rebuild.
What would be the best command to be able to proceed this step?
-
What exactly are you trying to do?
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 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply