Symptoms

Assume that you have database mirroring set up between a principal server and a mirror server, and that the principal and mirror servers are running on Microsoft SQL Server 2012, 2014 or 2016. During the redo phase of a large transaction on the mirror server, the redo thread cannot set an exclusive (X) lock and this generates an assert memory dump file. This issue may not be resolved even if you try to restart the SQL Server service on the mirror.

Resolution

This issue is fixed in the following cumulative updates for SQL Server:

Cumulative Update 5 for SQL Server 2016 RTM

Cumulative Update 2 for SQL Server 2016 SP1

Cumulative Update 7 for SQL Server 2012 Service Pack 3

Cumulative Update 11 for SQL Server 2014 SP1

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 install the latest cumulative updates for SQL Server:


Latest cumulative update for SQL Server 2016

Latest cumulative update for SQL Server 2014

Latest cumulative update for SQL Server 2012 SP3
 

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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×