Symptoms
Assume that you use the Always On Availability Group (AG) in Microsoft SQL Server 2019, and that AG database on the primary replica captures logs in Log Writer threads. If one Log Writer thread fails to send a log block, it will stop log capture on Log Writer threads and start a new log capture thread. In this situation, you may receive the following error message on the secondary replica:
Error: 19432, Severity: 16, State: 0.
Always On Availability Groups transport has detected a missing log block for availability database "DatabaseName". LSN of last applied log block is (xxxx.xxxxxxx.x). Log scan will be restarted to fix the issue. This is an informational message only. No user action is required.
Resolution
This issue is fixed in the following cumulative update for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology that Microsoft uses to describe software updates.
