checkdb error

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 Administration » checkdb error

checkdb error

Rate Topic

Display Mode

Topic Options

Author

Message

Ratheesh.K.Nair

Posted Friday, January 25, 2013 6:55 AM

SSCrazy

Group: General Forum Members
Last Login: Thursday, May 16, 2013 3:21 AM
Points: 2,415, Visits: 3,370

Hi experts,

CHECKDB threw error

Cannot insert duplicate key row in object 'sys.syscommittab' with unique index 'si_xdes_id'. The duplicate key value is (55822684521).

Post #1411697

GilaMonster

Posted Friday, January 25, 2013 7:38 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 2:27 AM
Points: 37,651, Visits: 29,905

Please run the following and post the full and complete, unedited output.

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1411727

Ratheesh.K.Nair

Posted Monday, January 28, 2013 7:34 AM

SSCrazy

Group: General Forum Members
Last Login: Thursday, May 16, 2013 3:21 AM
Points: 2,415, Visits: 3,370

Msg 2601, Level 14, State 1, Procedure sp_flush_commit_table, Line 15
Cannot insert duplicate key row in object 'sys.syscommittab' with unique index 'si_xdes_id'. The duplicate key value is (55822684521).
The statement has been terminated.
Msg 2601, Level 14, State 1, Procedure sp_flush_commit_table, Line 15
Cannot insert duplicate key row in object 'sys.syscommittab' with unique index 'si_xdes_id'. The duplicate key value is (55822684521).
Msg 5269, Level 16, State 1, Line 1
Check terminated. The transient database snapshot for database 'ABC' (database ID 8) has been marked suspect due to an IO operation failure. Refer to the SQL Server error log for details.
Msg 3999, Level 17, State 1, Line 1
Failed to flush the commit table to disk in dbid 8 due to error 2601. Check the errorlog for more information.
Msg 3999, Level 17, State 1, Line 1
Failed to flush the commit table to disk in dbid 8 due to error 2601. Check the errorlog for more information.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.

Post #1412434

Paul Randal

Posted Monday, January 28, 2013 7:45 AM

SSCommitted

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 1:23 PM
Points: 1,905, Visits: 1,601

Can you run the CHECKDB using WITH TABLOCK?

Can you also try creating a database snapshot of your database to see if that succeeds? (nothing to do with CHECKDB)

I suspect there's something amiss with it and when the snapshot creation starts, it's trying to roll back a transaction in the snapshot and failing.

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

Post #1412438

GilaMonster

Posted Monday, January 28, 2013 7:51 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 2:27 AM
Points: 37,651, Visits: 29,905

Check this out, see if it's applicable.
http://blogs.msdn.com/b/davidhardin/archive/2011/09/28/sql-server-2008-r2-change-tracking-and-backup-fix.aspx

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1412445

Ratheesh.K.Nair

Posted Tuesday, January 29, 2013 2:29 AM

SSCrazy

Group: General Forum Members
Last Login: Thursday, May 16, 2013 3:21 AM
Points: 2,415, Visits: 3,370

Thanks SQL Gurus Paul and Gail for the response.

Post #1412832

Ratheesh.K.Nair

Posted Tuesday, January 29, 2013 2:30 AM

SSCrazy

Group: General Forum Members
Last Login: Thursday, May 16, 2013 3:21 AM
Points: 2,415, Visits: 3,370

SNAPSHOT CREATION FAILED WITH BELOW ERROR
--------------------------------------------------------
Msg 2601, Level 14, State 1, Procedure sp_flush_commit_table, Line 15
Cannot insert duplicate key row in object 'sys.syscommittab' with unique index 'si_xdes_id'. The duplicate key value is (55822684521).
The statement has been terminated.
Msg 2601, Level 14, State 1, Procedure sp_flush_commit_table, Line 15
Cannot insert duplicate key row in object 'sys.syscommittab' with unique index 'si_xdes_id'. The duplicate key value is (55822684521).
The statement has been terminated.
Msg 3999, Level 17, State 1, Line 1
Failed to flush the commit table to disk in dbid 8 due to error 2601. Check the errorlog for more information.
Msg 3999, Level 17, State 1, Line 1
Failed to flush the commit table to disk in dbid 8 due to error 2601. Check the errorlog for more information.

DBCC CHECKDB WITH TABLOCK GAVE BELOW ERROR
---------------------------------------------------------------
Msg 5030, Level 16, State 12, Line 1
The database could not be exclusively locked to perform the operation.
Msg 7926, Level 16, State 1, Line 1
Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details.

Post #1412833

GilaMonster

Posted Tuesday, January 29, 2013 2:34 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 2:27 AM
Points: 37,651, Visits: 29,905

Ratheesh.K.Nair (1/29/2013)

DBCC CHECKDB WITH TABLOCK GAVE BELOW ERROR
---------------------------------------------------------------
Msg 5030, Level 16, State 12, Line 1
The database could not be exclusively locked to perform the operation.
Msg 7926, Level 16, State 1, Line 1
Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details.

Make sure there are no users in the database and try again. Tablock requires exclusive locks.

Definitely looking like it's not a checkDB problem. Did you read the blog post I referenced?

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1412835

Ratheesh.K.Nair

Posted Tuesday, January 29, 2013 2:51 AM

SSCrazy

Group: General Forum Members
Last Login: Thursday, May 16, 2013 3:21 AM
Points: 2,415, Visits: 3,370

Yes Gail I have go through the link you provided.

Mine is SQL Server 2008 R2 SP1 & CU3 and in that post its mentioned like fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 1.

Do i need to upgrade to SP2?

What I am worried now is all these requires restart.

Post #1412845

Ratheesh.K.Nair

Posted Tuesday, January 29, 2013 8:23 AM

SSCrazy

Group: General Forum Members
Last Login: Thursday, May 16, 2013 3:21 AM
Points: 2,415, Visits: 3,370

deleted

Post #1413076

« Prev Topic | Next Topic »

Permissions