Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 13198910
KB4515772 - FIX: Transaction log isn't truncated on a single node Availability Group in SQL Server - Microsoft Support
Last update date:
9/15/2021
Affected products:
SQL Server 2016 Service Pack 2
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
SQL Server 2017 Developer on Windows
SQL Server 2017 Enterprise Core on Windows
SQL Server 2017 Enterprise on Windows
SQL Server 2017 Standard on Windows
SQL Server 2019 on Windows
SQL Server 2016
SQL Server 2016 Service Pack 3 - duplicate (do not use)
Affected releases:
build lower than 15.0.4003.23
Fixed releases:
15.0.4003.23
Description:
Symptoms
Assume that you have an Always On Availability Group (AG) that has only a primary replica (no secondary replicas). Over time, you may encounter the following error message: Error 9002. The transaction log for database is full due to 'AVAILABILITY_REPLICA'. When you run a transaction log backup, the error won't be resolved because the log is not truncated, and it uses all the available space.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Resolution
This problem is fixed in the following cumulative updates for SQL Server: Cumulative Update 1 for SQL Server 2019 Cumulative Update 18 for SQL Server 2017 Cumulative Update 10 for SQL Server 2016 SP2 About cumulative updates for SQL Server: Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server: Latest cumulative update for SQL Server 2019 Latest cumulative update for SQL Server 2017 Latest cumulative update for SQL Server 2016
Service Pack Information for SQL Server 2016
This problem is fixed in the following service pack for SQL Server: Service Pack 3 for SQL Server 2016
References
Learn about the terminology that Microsoft uses to describe software updates.
