FIX: Database mirroring session is suspended in SQL Server 2005 and in SQL Server 2008 and in SQL Server 2008 R2 if the High-performance (asynchronous) mode is used

Consider the following scenario:

• You create a database mirroring session between two instances of SQL Server 2005 and SQL Server 2008 and SQL Server 2008 R2 by using the High-Performance (asynchronous) mode. One instance is the principal SQL Server that contains the principal database, and the other instance is the mirror SQL Server that contains the mirror database.
• A long delay occurs between the principal and mirror databases. For example, one of the following delays occurs:
  
  • The redo process of the mirror database is slower than the transfer of the transaction from the principal database to the mirror database.
  • A transaction that requires a long time runs on the principal database. For example, an ALTER INDEX REBUILD query runs on the principal database.

In this scenario, the session is suspended, and a mini-dump file is generated in the log folder on the mirror server. Additionally, one of the following is logged:

• Some messages that resemble the following and that are generated for an assertion failure are created in the log folder on the mirror server:
  
  <Date><Time> spid<ID> * BEGIN STACK DUMP:
  <Date><Time> spid<ID> * <Date><Time>spid <ID>
  <Date><Time> spid<ID> *
  <Date><Time> spid<ID> * Location: "logmgr.cpp":5565
  <Date><Time> spid<ID> * Expression: !(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)
  <Date><Time> spid<ID> * SPID: <ID>
  <Date><Time>spid<ID> * Process ID: <ID>
• If you have SQL Server 2005 Service Pack 3 (SP3) Cumulative Update 10 installed, the following error message is logged in the SQL Server error log on the mirror server:
  <Date><Time> spid<ID> Error: 9003, Severity: 20, State: 15.
  <Date> <Time> spid<ID> The log scan number (385562:137311:1) passed to log scan in database '<Database name>' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
  <Date><Time> spid<ID> Error: 1454, Severity: 16, State: 1.
  <Date><Time> spid<ID> While acting as a mirroring partner for database '<Database name>', server instance '<Database name>' encountered error 9003, status 15, severity 20. Database mirroring will be suspended. Try to resolve the error and resume mirroring.
  <Date><Time> spid<ID> Database mirroring is inactive for database '<Database name>'. This is an informational message only. No user action is required.
  <Date><Time> spid<ID> Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
  <Date><Time> spid<ID> Error: 1474, Severity: 16, State: 1.
  <Date><Time> spid<ID> Database mirroring connection error 4 '10650(error not found)' for 'TCP://<FQDN>:<Port>'.

Notes

• <FQDN> is a placeholder that represents the fully qualified domain name (FQDN) of the mirror server.
• <Port> is a placeholder that represents the port of the mirror server.

Cumulative update information

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 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: 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: Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 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 2008 R2

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 R2, click the following article number to view the article in the Microsoft Knowledge Base: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 R2 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:

SQL Server 2005 Service Pack 3

The fix for this issue was first released in Cumulative Update 13 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: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: 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.

SQL Server 2005 Service Pack 4

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

SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 13 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: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: 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.

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

For more information about a SQL Server assertion that is logged in the SQL Server Errorlog file when you restart the SQL Server service in SQL Server 2005, click the following article number to view the article in the Microsoft Knowledge Base:

981273  (http://support.microsoft.com/kb/981273 / ) FIX: A SQL Server assertion is logged in the SQL Server Errorlog file when you restart the SQL Server service in SQL Server 2005