You’re offline. This is a read only version of the page.
2 out of 18 Dynamics GP 2013 databases had backup failure, with error below.
Failed to flush the commit table to disk in dbid ____ due to error 2601.
Some research done on this error showed that it's related to the Change Tracking enabled on the database.
I then tried to turn off the Change Tracking for these 2 databases, but it gave me another error. (I only managed to capture the below from the log).
Cannot insert duplicate key row in object 'sys.syscommittab' with unique index
In this case, what else can be done to remove the Change Tracking, or at least to get the backup fixed ? (There has been no backup for 2 months now).
-------------------------------------------
Additional details of the environment:
1. Database Server (Standalone)
Windows Server 2012
SQL Server 2012 SP1
-------------------------------------------
*This post is locked for comments
Exactly... this is where i got stuck because i got no proof and explanation to the client... still owing them answers to the questions i posted earlier today..
Hi Soma,
The client environment is updated to SQL2012 SP1, so i think it may not be this bug after all ?
Ivan,
I think this is a bug in SQL server with enable Change Tracking (Backup database may failure if we enable change tracking). That's why Microsoft has provided the cumulative updates/Hot fixes for this issue.
Note: This error may occur in the below SQL server versions.
Microsoft SQL Server 2008 Service Pack 1 (SP1), Microsoft SQL Server 2008 Service Pack 2 (SP2), Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012.
Hope this helps!!!
Hi Nataraj,
Thanks for the link.
According to the article, for SQL2012 Cumulative Update 1 should already fix this error. This client environment is already updated to SP1 (11.0.3128), so it's supposed to be already fixed.
And since it didn't, hence the post here to inquire the solution and cause of the issue.
As at now, the issue has been resolved, pending now is the cause of the issue to revert to the client, and also on how to overcome this issue should this change tracking is required to be turned on. In other words, now that the environment is already in SQL2012 SP1, and to turn on the change tracking, would it cause the same issue yet again.
Ivan,
I guess by applying hot-fix for the latest version resolves your case. please have a look on the below article
Hi Soma,
Disabling change tracking did help, even though the disable process was quite tedious, going through each and every table.
Nevertheless, the backup is now working properly, but the next question would be why change tracking could cause such error in the first place, and how to overcome this should change tracking is required to be turned on.
Try to disable the change tracking for all the database and then run the backup again.
For your reference, have a look on the below link.
community.dynamics.com/.../attention-sql-backup-failed.aspx
Hope this helps!!!
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (