FIX: Error 1478 when you add a database back to the AlwaysOn availability group in SQL Server
Consider the following scenario:
- You use the AlwaysOn availability groups feature in Microsoft SQL Server 2012, 2014, or 2016.
- You back up a transaction log of a database while there are transaction log activities.
- The transaction log activities stop after the backup completed.
- You remove the database from the AlwaysOn availability group.
The issue was first fixed in the following cumulative update of SQL Server:
- Cumulative Update 1 for SQL Server 2014 SP2
- Cumulative Update 8 for SQL Server 2014 SP1
- Cumulative Update 1 for SQL Server 2016
- Cumulative Update 14 for SQL Server 2014
- Cumulative Update for 3 SQL Server 2012 SP3
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:
To work around this issue, create a transaction log backup on the primary replica, restore the log backup on the secondary replica with no recovery, and then rejoin the secondary replica to the AlwaysOn availability group.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology Microsoft uses to describe software updates.
Article ID: 3152965 - Last Review: 08/25/2016 16:32:00 - Revision: 8.0
Microsoft SQL Server 2012 Service Pack 3, Microsoft SQL Server 2014 Developer, Microsoft SQL Server 2014 Enterprise, Microsoft SQL Server 2014 Enterprise Core, Microsoft SQL Server 2014 Express, Microsoft SQL Server 2014 Standard, Microsoft SQL Server 2014 Web, Microsoft SQL Server 2016 Developer, Microsoft SQL Server 2016 Enterprise, Microsoft SQL Server 2016 Enterprise Core, Microsoft SQL Server 2016 Standard
- kbqfe kbfix kbsurveynew kbexpertiseadvanced KB3152965