Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Cannot insert duplicate key row in object 'sys.syscommittab' Expand / Collapse
Author
Message
Posted Monday, June 6, 2011 8:22 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, March 5, 2012 5:44 AM
Points: 8, Visits: 135
Hi there

I have a SQL Server 2008 R2 on a windows 2008 server.
After one failed backup, I started getting these errors:

Error: 2601, Severity: 14, State: 1.
Cannot insert duplicate key row in object 'sys.syscommittab' with unique index 'si_xdes_id'.
Error: 3999, Severity: 17, State: 1.
Failed to flush the commit table to disk in dbid 5 due to error 2601. Check the errorlog for more information.

From Microsoft, I found this:
A backup Operation On A SQL Server 2008 Database Fails If You Enable Change Tracking On This Database
http://support.microsoft.com/kb/978839

But this bug refers to SQL Server 2008. What should I do if in my case is a R2 version?

Thanks in advance

Post #1120298
Posted Monday, June 6, 2011 9:01 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Friday, June 27, 2014 12:43 PM
Points: 15,444, Visits: 9,596
Since the fix involved either applying a CU (probably not applicable to R2), or restarting change tracking, I'd either contact Microsoft support and ask about the CU, or restart change tracking if you can do that.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #1120320
Posted Monday, June 6, 2011 9:18 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, March 5, 2012 5:44 AM
Points: 8, Visits: 135
I've already did bit it didn't work.
What I did now was to disable the change tracking, do backup, and enable the change tracking again.
It seems is working well now.

Thanks.
Post #1120336
Posted Tuesday, June 7, 2011 6:16 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Friday, June 27, 2014 12:43 PM
Points: 15,444, Visits: 9,596
Good to know it can be a problem in R2, and that there's an easy way to resolve it.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #1120919
Posted Friday, September 6, 2013 7:42 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, September 23, 2013 9:32 AM
Points: 2, Visits: 20
I faced same problem as you described. Then I disabled and enabled Change Tracking, installed latest service pack with no success, Nothing was the solution for my case.

Then I followed below way. It solved the problem.

1.Put database single user mode.
2.Create a DAC Connection to database. For DAC info click here.
3.Run this : DBCC CHECKTABLE("sys.syscommittab", REPAIR_REBUILD)
4.Put database multi user mode.
Post #1492239
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse