Article ID: 956017 - Last Review: March 19, 2009 - Revision: 2.0

You cannot resume a database mirroring session after you perform a rolling upgrade from SQL Server 2005 to SQL Server 2008 if the mirrored database contains a full-text index

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Expand all | Collapse all

SYMPTOMS

You create a database mirroring session of Microsoft SQL Server 2005. The mirrored database contains a full-text index. Then, on the server instances that are involved in the database mirroring session, you perform a rolling upgrade from SQL Server 2005 to Microsoft SQL Server 2008. After the rolling upgrade, the mirrored database is suspended instead of being synchronized. When you try to resume the database mirroring session on the new principal server, the resume operation fails. Additionally, you experience the following issues:
  • On the new principal server, the following error message is logged in the SQL Server Errorlog file:
    <Date><Time> spid14s Error: 1453, Severity: 16, State: 1.
    <Date><Time> spid14s 'TCP://<ServerName>', the remote mirroring partner for database '<DatabaseName>', encountered error 5180, status 1, severity 22. Database mirroring has been suspended. Resolve the error on the remote server and resume mirroring, or remove mirroring and re-establish the mirror server instance.
    Note In this error message, <ServerName> represents the name or the IP address of the new mirror server. And, <DatabaseName> represents the name of the mirrored database.
  • On the new principal server, you open SQL Server Management Studio and connect to the instance of SQL Server 2008. When you expand Databases in Object Explorer, you notice that the (Principal, Suspended) text appears next to the name of the mirrored database.

    Note If the resume operation succeeds, the (Principal, Synchronized) text appears next to the name of the mirrored database.
  • On the new mirror server, the following error message is logged in the SQL Server Errorlog file:
    <Date> <Time> spid24s Error: 5180, Severity: 22, State: 1.
    <Date><Time> spid24s Could not open File Control Bank (FCB) for invalid file ID 3 in database '<DatabaseName>''. Verify the file location. Execute DBCC CHECKDB.
    <Date><Time> spid24s Error: 1454, Severity: 16, State: 1.
    <Date><Time> spid24s Database mirroring will be suspended. Server instance '<ServerName>' encountered error 5180, state 1, severity 22 when it was acting as a mirroring partner for database '<DatabaseName>'. The database mirroring partners might try to recover automatically from the error and resume the mirroring session. For more information, view the error log for additional error messages.
Back to the top

WORKAROUND

To work around this problem, follow these steps:
  1. On the new mirror server, enable trace flag 3499 by running the following statement:
    DBCC TRACEON (3499, -1)
    GO
  2. On the new principal server, resume the database mirroring session by running the following statement:
    ALTER DATABASE <DatabaseName>
SET PARTNER RESUME
GO

    After you run this statement, examine the name of the mirrored database in SQL Server Management Studio. Make sure that the (Principal, Synchronized) text appears next to the name of the mirrored database.
  3. On the new mirrored server, disable the trace flag by running the following statement:
    DBCC TRACEOFF(3499, -1)
GO
Back to the top

STATUS

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

REFERENCES

For more information about the sys.database_mirroring catalog view, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/ms178655(sql.100).aspx (http://msdn.microsoft.com/en-us/library/ms178655(sql.100).aspx)
For more information about how to view the state of a mirrored database, visit the following MSDN Web site:
http://msdn.microsoft.com/en-us/library/ms187050(SQL.100).aspx (http://msdn.microsoft.com/en-us/library/ms187050(SQL.100).aspx)
For more information about a rolling upgrade, visit the following MSDN Web site:
http://msdn.microsoft.com/en-us/library/bb677181(SQL.100).aspx (http://msdn.microsoft.com/en-us/library/bb677181(SQL.100).aspx)
For more information about how to upgrade full-text search to SQL Server 2008, visit the following MSDN Web site:
http://msdn.microsoft.com/en-us/library/ms142490(SQL.100).aspx (http://msdn.microsoft.com/en-us/library/ms142490(SQL.100).aspx)
For more information about the DBCC TRACEON statement, visit the following MSDN Web site:
http://msdn.microsoft.com/en-us/library/ms187329(sql.100).aspx (http://msdn.microsoft.com/en-us/library/ms187329(sql.100).aspx)
For more information about the DBCC TRACEOFF statement, visit the following MSDN Web site:
http://msdn.microsoft.com/en-us/library/ms174401(SQL.100).aspx (http://msdn.microsoft.com/en-us/library/ms174401(SQL.100).aspx)
Back to the top
APPLIES TO
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Standard
Back to the top
Keywords: 
sql2008relnoteconfiguration sql2008relnotecluster sql2008relnote kbexpertiseadvanced kbtshoot kbprb KB956017
Back to the top