Error 605 from the sqlserver

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Hans Olav Nymand
Posts: 55
Joined: Wed Sep 29, 2004 8:09 am
Location: Denmark, Copenhagen
Contact:

Error 605 from the sqlserver

Post by Hans Olav Nymand » Thu Dec 15, 2005 2:35 am

Hi, vi now experience the following errors from the sqlserver during branching (most cases, but not all) and some times during "view history" (sometimes, but typically it works)

Vault shows the following errors:
[14-12-2005 14:09:18] An exception was encountered during the transaction. Exception: Exception of type System.Exception was thrown. at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, Boolean keepCheckedOut, Boolean removeLocalCopy, Boolean bIsImport, DateTime dateImport, Int32 nUserIDImport, Int64& nRevID)
[14-12-2005 14:09:18] Transaction failed
[14-12-2005 14:09:18] Item $/Interfaces/Src/PdcTransactions caused the transaction to fail: A database error has occured (FailDBFault)

The sqlserver log show the following errors:
2005-12-14 14:09:15.58 spid51 Error: 605, Severity: 21, State: 1
2005-12-14 14:09:15.58 spid51 Attempt to fetch logical page (1:868680) in database 'sgvault' belongs to object 'tblfolderentries', not to object 'tblbranchedhistoryitems'..

A "DBCC CHECKDB" shows that two tables are error-prone:
* Table tbllisencekeys: 3 errors
* Table tblbranchedhistoryitems: 13 errors

The DBCC commands also tells the follwowing:
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (sgvault ).

Can you advise us on what to do?

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Thu Dec 15, 2005 6:36 am

You'll need to stop Vault for a bit while we diagnose the database (iisreset.exe /stop)

Can you try to stop / start SQL Server, and then run DBCC CHECKDB again? If you have multiple SQL Server engines running, please ensure you recycle the correct database engine.

Report any messages from the second run.
Jeff Clausius
SourceGear

Hans Olav Nymand
Posts: 55
Joined: Wed Sep 29, 2004 8:09 am
Location: Denmark, Copenhagen
Contact:

Post by Hans Olav Nymand » Thu Dec 15, 2005 7:03 am

Hi,

Vault web service is stopped.

SQL Server stopped and started.

DBCC CHECKDB results follows:
DBCC results for 'sgvault'.
DBCC results for 'sysobjects'.
There are 633 rows in 14 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 272 rows in 16 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
There are 1978 rows in 50 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 51 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 538 rows in 344 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 49 rows in 1 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 15 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 20 rows in 1 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 2936 rows in 20 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 114 rows in 1 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
DBCC results for 'tblfolderentrypins'.
There are 422 rows in 2 pages for object 'tblfolderentrypins'.
DBCC results for 'tblfsobjectattrs'.
There are 0 rows in 0 pages for object 'tblfsobjectattrs'.
DBCC results for 'tblfsobjectattrvalues'.
There are 0 rows in 0 pages for object 'tblfsobjectattrvalues'.
DBCC results for 'tblfsobjecthistoryitemmisc'.
There are 476644 rows in 4135 pages for object 'tblfsobjecthistoryitemmisc'.
DBCC results for 'tblfsobjecthistoryitems'.
There are 945304 rows in 5942 pages for object 'tblfsobjecthistoryitems'.
DBCC results for 'tblfsobjectorigins'.
There are 108063 rows in 724 pages for object 'tblfsobjectorigins'.
DBCC results for 'tblfsobjects'.
There are 464183 rows in 2487 pages for object 'tblfsobjects'.
DBCC results for 'tblfsobjectversionattrs'.
There are 0 rows in 0 pages for object 'tblfsobjectversionattrs'.
DBCC results for 'tblfsobjectversionattrvalues'.
There are 0 rows in 0 pages for object 'tblfsobjectversionattrvalues'.
DBCC results for 'tblfsobjectversionorigattrvalues'.
There are 0 rows in 0 pages for object 'tblfsobjectversionorigattrvalues'.
DBCC results for 'tblfsobjectversionfileinfos'.
There are 515244 rows in 3002 pages for object 'tblfsobjectversionfileinfos'.
DBCC results for 'tblfsobjectversionnames'.
There are 465035 rows in 2904 pages for object 'tblfsobjectversionnames'.
DBCC results for 'tblfsobjectversions'.
There are 1192588 rows in 9319 pages for object 'tblfsobjectversions'.
DBCC results for 'tblfulltreerevisionfolders'.
There are 92 rows in 2 pages for object 'tblfulltreerevisionfolders'.
DBCC results for 'tblgroups'.
There are 16 rows in 1 pages for object 'tblgroups'.
DBCC results for 'tblgroupmembers'.
There are 133 rows in 1 pages for object 'tblgroupmembers'.
DBCC results for 'tbllicensekeys'.
There are 6 rows in 1 pages for object 'tbllicensekeys'.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:868239) allocated to object ID 2009058193, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:868679) allocated to object ID 2009058193, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:868680) allocated to object ID 2009058193, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:868681) allocated to object ID 2009058193, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
DBCC results for 'tblmergeablefileextensions'.
There are 893 rows in 8 pages for object 'tblmergeablefileextensions'.
DBCC results for 'tblrepositories'.
There are 19 rows in 1 pages for object 'tblrepositories'.
DBCC results for 'tblfsobjectlabelviews'.
There are 794691 rows in 12005 pages for object 'tblfsobjectlabelviews'.
DBCC results for 'tbltransactiondetailattrs'.
There are 1 rows in 1 pages for object 'tbltransactiondetailattrs'.
DBCC results for 'tblfsobjectlabels'.
There are 301 rows in 8 pages for object 'tblfsobjectlabels'.
DBCC results for 'tbltransactiondetailattrvalues'.
There are 37969 rows in 665 pages for object 'tbltransactiondetailattrvalues'.
DBCC results for 'tbltransactiondetails'.
There are 480231 rows in 3714 pages for object 'tbltransactiondetails'.
DBCC results for 'tbltransactionattrs'.
There are 1 rows in 1 pages for object 'tbltransactionattrs'.
DBCC results for 'tbltransactionattrvalues'.
There are 6891 rows in 120 pages for object 'tbltransactionattrvalues'.
DBCC results for 'tbltransactions'.
There are 96828 rows in 503 pages for object 'tbltransactions'.
DBCC results for 'tmpfsobjectshares2'.
There are 723 rows in 17 pages for object 'tmpfsobjectshares2'.
DBCC results for 'tblfsobjectshares'.
There are 1640 rows in 39 pages for object 'tblfsobjectshares'.
DBCC results for 'tblschemaversions'.
There are 1 rows in 1 pages for object 'tblschemaversions'.
DBCC results for 'tblfsobjectlabelchanges'.
There are 178 rows in 2 pages for object 'tblfsobjectlabelchanges'.
DBCC results for 'tblsessions'.
There are 20 rows in 4 pages for object 'tblsessions'.
DBCC results for 'tblusers'.
There are 68 rows in 3 pages for object 'tblusers'.
DBCC results for 'tblusersecuritychanges'.
There are 1292 rows in 9 pages for object 'tblusersecuritychanges'.
DBCC results for 'tblfsobjectlabelchangedeltas'.
There are 7895 rows in 134 pages for object 'tblfsobjectlabelchangedeltas'.
DBCC results for 'tblvaultsettings'.
There are 1 rows in 1 pages for object 'tblvaultsettings'.
DBCC results for 'tbltreerevisionfolderdeltas'.
There are 1395083 rows in 15213 pages for object 'tbltreerevisionfolderdeltas'.
DBCC results for 'tbluserrepositories'.
There are 1254 rows in 5 pages for object 'tbluserrepositories'.
DBCC results for 'tbltreerevisionfolders'.
There are 172190 rows in 1360 pages for object 'tbltreerevisionfolders'.
DBCC results for 'tblsessionlabelqueries'.
There are 0 rows in 1 pages for object 'tblsessionlabelqueries'.
DBCC results for 'tblfsobjectshares_3102'.
There are 723 rows in 42 pages for object 'tblfsobjectshares_3102'.
DBCC results for 'tblsessionrecursivelabelqueries'.
There are 0 rows in 1 pages for object 'tblsessionrecursivelabelqueries'.
DBCC results for 'tblpendingtransactionobjects'.
There are 0 rows in 1 pages for object 'tblpendingtransactionobjects'.
DBCC results for 'tblsecurityassignments'.
There are 169 rows in 1 pages for object 'tblsecurityassignments'.
DBCC results for 'tblsecurityassignmentspaths'.
There are 55 rows in 1 pages for object 'tblsecurityassignmentspaths'.
DBCC results for 'tblplugins'.
There are 0 rows in 0 pages for object 'tblplugins'.
DBCC results for 'tblwatchers'.
There are 15 rows in 2 pages for object 'tblwatchers'.
DBCC results for 'tblfilefolderexclusions'.
There are 418 rows in 2 pages for object 'tblfilefolderexclusions'.
DBCC results for 'tbltransactionfsobjectversions'.
There are 0 rows in 1 pages for object 'tbltransactionfsobjectversions'.
DBCC results for 'tbldelayusersecuritychanges'.
There are 0 rows in 0 pages for object 'tbldelayusersecuritychanges'.
DBCC results for 'dtproperties'.
There are 0 rows in 0 pages for object 'dtproperties'.
DBCC results for 'tbldelaysecurityassignments'.
There are 0 rows in 0 pages for object 'tbldelaysecurityassignments'.
DBCC results for 'tbltransactionrepositorycounts'.
There are 0 rows in 1 pages for object 'tbltransactionrepositorycounts'.
DBCC results for 'tblbackups'.
There are 0 rows in 0 pages for object 'tblbackups'.
DBCC results for 'tblkeywordextensions'.
There are 456 rows in 2 pages for object 'tblkeywordextensions'.
DBCC results for 'tblbranchedhistoryitems'.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:868682) allocated to object ID 2009058193, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2009058193, index ID 1. Page (1:868224) is missing a reference from previous page (1:868239). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 2009058193, index ID 1. Page (1:868239) was not seen in the scan although its parent (1:868240) and previous (1:868238) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2009058193, index ID 1. Page (1:868664) is missing a reference from previous page (1:868679). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 2009058193, index ID 1. Page (1:868679) was not seen in the scan although its parent (1:870033) and previous (1:868678) refer to it. Check any previous errors.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 2009058193, index ID 1. Page (1:868680) was not seen in the scan although its parent (1:870033) and previous (1:868695) refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 2009058193, index ID 1. Index node page (1:870033), slot 208 refers to child page (1:868681) and previous child (1:868680), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 2009058193, index ID 1. Index node page (1:870033), slot 209 refers to child page (1:868682) and previous child (1:868681), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2009058193, index ID 1. Page (1:868683) is missing a reference from previous page (1:868682). Possible chain linkage problem.
There are 350463 rows in 1206 pages for object 'tblbranchedhistoryitems'.
CHECKDB found 0 allocation errors and 13 consistency errors in table 'tblbranchedhistoryitems' (object ID 2009058193).
DBCC results for 'tblclientoptions'.
There are 4769 rows in 47 pages for object 'tblclientoptions'.
DBCC results for 'tblcloaks'.
There are 250 rows in 9 pages for object 'tblcloaks'.
DBCC results for 'tbldeletedfsobjects'.
There are 182974 rows in 809 pages for object 'tbldeletedfsobjects'.
DBCC results for 'tblcheckoutlists'.
There are 2790 rows in 17 pages for object 'tblcheckoutlists'.
DBCC results for 'tbldeletions'.
There are 7484 rows in 50 pages for object 'tbldeletions'.
DBCC results for 'tblcheckoutlistitems'.
There are 711305 rows in 26463 pages for object 'tblcheckoutlistitems'.
DBCC results for 'tbleolconversion'.
There are 5 rows in 1 pages for object 'tbleolconversion'.
DBCC results for 'tblfileinfo'.
There are 444961 rows in 2753 pages for object 'tblfileinfo'.
DBCC results for 'tblfolderentries'.
There are 9893636 rows in 34105 pages for object 'tblfolderentries'.
DBCC results for 'tblloginattempts'.
There are 0 rows in 1 pages for object 'tblloginattempts'.
CHECKDB found 0 allocation errors and 13 consistency errors in database 'sgvault'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (sgvault ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.


Regards,
Hans Olav

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Thu Dec 15, 2005 8:48 am

Hans:

I'm still researching the issue. In the meantime, how old is your last backup of the Vault database?
Jeff Clausius
SourceGear

Hans Olav Nymand
Posts: 55
Joined: Wed Sep 29, 2004 8:09 am
Location: Denmark, Copenhagen
Contact:

Post by Hans Olav Nymand » Thu Dec 15, 2005 8:51 am

Hi,

We have daily backups :D. Tomorrow we are going to try to restore some of the backups to run DBCC on the backed-up databases.

Regards,
Hans Olav

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Thu Dec 15, 2005 8:52 am

Hans:

Before we resort to a restoration, I want to try something. What version of Vault server is installed?
Jeff Clausius
SourceGear

Hans Olav Nymand
Posts: 55
Joined: Wed Sep 29, 2004 8:09 am
Location: Denmark, Copenhagen
Contact:

Post by Hans Olav Nymand » Thu Dec 15, 2005 8:53 am

Hi,

Our VaultServer is version 3.1.2.3511

And don't worry about the backups - we're not ditching the current database yet, just evaluating the state of our backups.


Regards,
Hans Olav

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Thu Dec 15, 2005 9:16 am

If these links are problems in an index/key, we might be able to get around this.

While the Vault server is still disabled, could you please run this SQL Script:

Code: Select all

--For Vault 3.1.2.3511
USE [sgvault]
GO

ALTER TABLE [dbo].[tbllicensekeys] DROP CONSTRAINT [pk_tbllicensekeys]
GO

ALTER TABLE [dbo].[tbllicensekeys] WITH NOCHECK ADD
CONSTRAINT [pk_tbllicensekeys] PRIMARY KEY CLUSTERED
(
	[licensekey]
) ON [DEFAULT]
GO

ALTER TABLE [dbo].[tblbranchedhistoryitems] DROP CONSTRAINT [pk_tblbranchedhistoryitems]
GO

DROP INDEX [dbo].[tblbranchedhistoryitems].[idxbranchedhistoryitemsobjid]
GO

ALTER TABLE [dbo].[tblbranchedhistoryitems] WITH NOCHECK ADD
	CONSTRAINT [pk_tblbranchedhistoryitems] PRIMARY KEY CLUSTERED 
( 
	[histitemid], 
	[objid]
) ON [DEFAULT] 
GO

CREATE INDEX [idxbranchedhistoryitemsobjid] ON [dbo].[tblbranchedhistoryitems]
(
	[objid]
) ON [PRIMARY] 
After the script completes, run the DBCC CHECKDB command. Are the results any different?
Jeff Clausius
SourceGear

Hans Olav Nymand
Posts: 55
Joined: Wed Sep 29, 2004 8:09 am
Location: Denmark, Copenhagen
Contact:

Post by Hans Olav Nymand » Thu Dec 15, 2005 9:31 am

Hi,

I still get the following result:

Attempt to fetch logical page (1:868239) in database 'sgvault' belongs to object 'tblfolderentries', not to object 'tblbranchedhistoryitems'.
ODBC: Msg 0, Level 16, State 1


Regards,
Hans Olav

Hans Olav Nymand
Posts: 55
Joined: Wed Sep 29, 2004 8:09 am
Location: Denmark, Copenhagen
Contact:

Post by Hans Olav Nymand » Thu Dec 15, 2005 9:33 am

Sorry, that was very inprecise:

During the commands:
ALTER TABLE [dbo].[tblbranchedhistoryitems] WITH NOCHECK ADD
CONSTRAINT [pk_tblbranchedhistoryitems]

CREATE INDEX [idxbranchedhistoryitemsobjid] ON [dbo].[tblbranchedhistoryitems]

I get the error:
Server: Msg 605, Level 21, State 1, Line 1
Attempt to fetch logical page (1:868239) in database 'sgvault' belongs to object 'tblfolderentries', not to object 'tblbranchedhistoryitems'.

(But the constraint and index now are dropped)



Regards,
Hans Olav

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Thu Dec 15, 2005 9:42 am

OK. We might need that info later.

Does DBCC CHECKDB still have errors?
Jeff Clausius
SourceGear

Hans Olav Nymand
Posts: 55
Joined: Wed Sep 29, 2004 8:09 am
Location: Denmark, Copenhagen
Contact:

Post by Hans Olav Nymand » Thu Dec 15, 2005 9:44 am

Yes, DBCC CHECKDB still gives errors.

No more errors for 'tblicensekeys'

And errors for 'tblbranchedhistoryitems' are reduced from 13 errors to 5 errors - so I assume it had 8 errors in the index and the remaining 5 are in the data themselves.


Regards,
Hans Olav

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Thu Dec 15, 2005 9:48 am

Does the error message still state that repair_allow_data_loss is the minimum level to be used?
Jeff Clausius
SourceGear

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Thu Dec 15, 2005 10:11 am

If so, then I suspect we're going to have to use a backup or lose the history data.

Additional research of SQL Server suggests this might be caused when write-caching is enabled on your disk sub system. You may want to check this setting in the Drive's properties from Device Manager. If it is enabled, you may want to disable the setting. It will slow things down some, but at least the data should still be safe.
Jeff Clausius
SourceGear

Hans Olav Nymand
Posts: 55
Joined: Wed Sep 29, 2004 8:09 am
Location: Denmark, Copenhagen
Contact:

Post by Hans Olav Nymand » Thu Dec 15, 2005 11:18 am

Hi Jef,


Yes, DBCC still states that the repair_allow_data_loss is the minimum required repair level.

We'll try the backups. Thank you for your effort, and thanks for the hint on the disk-settings.


Regards,
Hans Olav

Post Reply