FIX: The removal of a transaction log file of the database on the principal server breaks a database mirroring session in SQL Server 2005 or in SQL Server 2008

Article translations Article translations
Article ID: 972681 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 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 2008 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • In Microsoft SQL Server 2005, SQL Server 2008, or in Microsoft SQL Server 2008 Service Pack 1 (SP1), you configure database mirroring between 2 databases.
  • You run the ALTER DATABASE command together with the REMOVE FILE clause to remove a transaction log file of the database on the principal server.
In this scenario, the Database Mirroring session is suspended and cannot resume, and you receive the following assertion:
Location: "logmgr.cpp":3350
Expression: headLFCB->lfcb_startOffset < fcb->GetSize () * (ULONGLONG)PAGESIZE

Additionally, the following error messages are logged in the SQL Server error log file:
<Date><Time> spid23s **Dump thread - spid = 23, PSS = 0x0000000082FBAB60, EC = 0x00000000837E81C0
<Date><Time> spid23s ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0007.txt
<Date><Time> spid23s * *******************************************************************************
<Date><Time> spid23s *
<Date><Time> spid23s * BEGIN STACK DUMP:
<Date><Time> spid23s * 01/27/09 14:39:23 spid 23
<Date><Time> spid23s *
<Date><Time> spid23s * Location: "logmgr.cpp":3350
<Date><Time> spid23s * Expression: headLFCB->lfcb_startOffset < fcb->GetSize () *
(ULONGLONG)PAGESIZE
<Date><Time> spid23s * SPID: 23
<Date><Time> spid23s * Process ID: 2260
...
<Date><Time> spid23s Stack Signature for the dump is 0x00000001308986EE
<Date><Time> spid23s External dump process return code 0x20000001.
External dump process returned no errors.
<Date><Time> spid23s Error: 17066, Severity: 16, State: 1.
<Date><Time> spid23s SQL Server Assertion: File: <"logmgr.cpp">, line=3350 Failed
Assertion = 'headLFCB->lfcb_startOffset < fcb->GetSize () * (ULONGLONG)PAGESIZE'. 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> spid23s Error: 3624, Severity: 20, State: 1.
<Date><Time> spid23s 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> spid23s Error: 1454, Severity: 16, State: 1.
<Date><Time> spid23s While acting as a mirroring partner for database '<databasename>', server instance '<instancename>' encountered error 3624, status 1, severity 20. Database mirroring will be suspended. Try to resolve the error and resume mirroring.
<Date><Time> spid23s Database mirroring is inactive for database '<databasename>'. This is an informational message only. No user action is required.

CAUSE

This problem occurs because of incorrect log space tracking on the mirror database.

RESOLUTION

SQL Server 2008

Important You must install this hotfix if you are running the release version of SQL Server 2008.

The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
971490 Cumulative update package 6 for SQL Server 2008
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 2008 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:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released

SQL Server 2008 Service Pack 1 (SP1)

Important You must install this hotfix if you are running SQL Server 2008 Service Pack 1 (SP1).

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
971491 Cumulative update package 3 for SQL Server 2008 Service Pack 1
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 2008 fix release. Microsoft recommends 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:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 Service Pack 2 (SP2)

Important You must install this hotfix if you are running SQL Server 2005 Service Pack 2 (SP2).

The fix for this issue was first released in Cumulative Update 15 for SQL Server 2005 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
972510 Cumulative update package 15 for SQL Server 2005 Service Pack 2
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. Microsoft recommends 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:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 Service Pack 3 (SP3)

The fix for this issue was first released in Cumulative Update 6 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
974648 Cumulative update package 6 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. Microsoft recommends 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
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

WORKAROUND

To work around this problem, remove and then re-create the database mirroring session. This operation requires a full database backup and restore.

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 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: 972681 - Last Review: August 17, 2009 - Revision: 2.1
APPLIES TO
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Workgroup Edition
Keywords: 
kbsurveynew kbexpertiseadvanced kbqfe kbfix KB972681

Give Feedback

 

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