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 | 12996125
KB4513237 - FIX: Async secondary replica receives logs from primary replica in SQL Server 2017 on Linux but it does not harden or redone - Microsoft Support
Last update date:
6/2/2022
Affected products:
SQL Server 2017 Developer
SQL Server 2017 Enterprise Core
SQL Server 2017 Enterprise
SQL Server 2017 Standard on Windows
SQL Server 2017 Standard on Linux
Affected releases:
build lower than 14.0.3223.3
Fixed releases:
14.0.3223.3
Description:
Symptoms
Async secondary replica can receive the log from primary replica in SQL Server 2017 on Linux. However, it does not harden or redone.
More Information
You can query last_redone_lsn and last_redone_time from sys.dm_hadr_database_replica_states on secondary replica to check whether it is progressing or not.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Resolution
This issue is fixed in the following cumulative update for SQL Server: Cumulative Update 16 for SQL Server 2017 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 2017
Workaround
To work around this issue, you can use one of the following methods: Pausing and resuming the data movement on secondary replica will make the pending changes applied. Restarting SQL Server on secondary replica will also make the pending changes applied.
References
Learn about the terminology that Microsoft uses to describe software updates.
