FIX: Secondary databases in a secondary replica may be in an "unknown" state if you join the secondary replica into availability groups two times in SQL Server 2012

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

On This Page

Symptoms

Consider the following scenario:
  • You have an instance of Microsoft SQL Server 2012 that has the AlwaysOn Availability Groups feature enabled.
  • You add several availability groups (AGs) to the instance.
  • You join a secondary replica into these AGs two times.
In this scenario, the secondary databases in the secondary replica may be in "unknown" state. Additionally, the data movements stop, and the secondary databases cannot be accessed when the corresponding primary replica is disconnected.
Back to the top | Give Feedback

Resolution

Cumulative update information

SQL Server 2012

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2012. For more information about how to obtain this cumulative update package for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
2679368
(http://support.microsoft.com/kb/2679368/ )
Cumulative update 1 for SQL Server 2012
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 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:
2692828
(http://support.microsoft.com/kb/2692828/ )
The SQL Server 2012 builds that were released after SQL Server 2012 was released
Back to the top | Give Feedback

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 | Give Feedback

Workaround

To work around this issue, bring the secondary databases online, and then rejoin the secondary replica into the AGs.
Back to the top | Give Feedback

References

For more information about the AlwaysOn Availability Groups feature, visit the following Microsoft Developer Network (MSDN) website:
General information about AlwaysOn Availability Groups
(http://msdn.microsoft.com/en-us/library/ff877884%28v=SQL.110%29.aspx)
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
(http://support.microsoft.com/kb/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
(http://support.microsoft.com/kb/822499/ )
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
(http://support.microsoft.com/kb/824684/ )
Description of the standard terminology that is used to describe Microsoft software updates
Back to the top | Give Feedback

Properties

Article ID: 2689367 - Last Review: November 19, 2012 - Revision: 2.0
Applies to
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Developer
  • SQL Server 2012 Enterprise Core
Keywords: 
kbtshoot kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2689367
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top