Error message when you shrink data files on principal in a Database Mirroring for two SQL Server 2005 servers

Article translations Article translations
Close Close
Article ID: 982933 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
Expand all | Collapse all

On This Page

Symptoms

You shrink data files on principal in a Database Mirroring for two Microsoft SQL Server 2005 servers. In this situation, you may encounter a SQL Server Assertion. Additionally, you find an error message that resembles the following in the SQL Server error log:
<Date Time> spid<ID>s Using 'dbghelp.dll' version '4.0.5'
<Date Time> spid<ID>s **Dump thread - spid = <ID>, PSS = 0x0000000080AE4B60, EC = 0x00000006D62141C0
<Date Time> spid<ID>s ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump<XXXX>.txt <Date Time> spid<ID>s ********************************************************************************

<Date Time> spid<ID>s *
<Date Time> spid<ID>s * BEGIN STACK DUMP:
<Date Time> spid<ID>s * <Date Time> spid <SPID>
<Date Time> spid<ID>s *
<Date Time> spid<ID>s * Location: loglock.cpp:834
<Date Time> spid<ID>s * Expression: result == LCK_OK
<Date Time> spid<ID>s * SPID: <SPID>
<Date Time> spid<ID>s * Process ID: <ProcessID>
...
...
<Date Time> spid<ID>s Error: 17066, Severity: 16, State: 1.
<Date Time> spid<ID>s SQL Server Assertion: File: <loglock.cpp>, line=834 Failed Assertion = 'result == LCK_OK'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
<Date Time> spid<ID>s Error: 3624, Severity: 20, State: 1.
<Date Time> spid<ID>s A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
<Date Time> spid<ID>s Error: 1454, Severity: 16, State: 1.
<Date Time> spid<ID>s While acting as a mirroring partner for database '<Database>', server instance '<Instance>' encountered error 3624, status 1, severity 20. Database mirroring will be suspended. Try to resolve the error and resume mirroring.
<Date Time> spid<ID>s Database mirroring is inactive for database '<Database>'. This is an informational message only. No user action is required.
Note When the issue occurs, a mini-dump is generated with name "SQLDump<XXXX>.dump" in the SQL Server error log folder.

Cause

This issue occurs because of a conflict between two transactions on the mirror. During regular processing on the principal, Database Console Commands (DBCC) Shrink operation starts a transaction. This transaction obtains a SCH_M heap or B-Tree (HoBT) lock and then releases that lock before the transaction commits. Another transaction obtains the IX lock on that heap or B-Tree before the first transaction commits. However, the heap or B-Tree lock is released during the first transaction is not logged. This causes a conflict on the mirror as the first transaction still owns the SCH_M lock on the heap or B-Tree.

Resolution

SQL Server 2005 Service Pack 3

The fix for this issue was first released in Cumulative Update 10. For more information about how to obtain this cumulative update package for SQL Server 2005, click the following article number to view the article in the Microsoft Knowledge Base:
983329 Cumulative update package 10 for SQL Server 2005 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

For more information about the SQL Server Error Log, visit the following Microsoft Developer Network (MSDN) website:
Viewing the SQL Server error log
For more information about Database Mirroring, visit the following MSDN website:
Overview of Database Mirroring
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 982933 - Last Review: October 24, 2013 - Revision: 5.0
Applies to
  • Microsoft SQL Server 2005 Service Pack 3
Keywords: 
kbnosurvey kbarchive kbsurveynew kbqfe kbfix kbexpertiseadvanced KB982933

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com