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 | 3004867
KB4458880 - FIX: "9003 error, sev 20, state 1" error when a backup operation fails on a secondary replica that is running in asynchronous-commit mode - Microsoft Support
Last update date:
4/11/2024
Affected products:
SQL Server 2016 Developer
SQL Server 2016 Enterprise
SQL Server 2016 Enterprise Core
SQL Server 2016 Standard
SQL Server 2017 on Windows (all editions)
SQL Server 2017 on Linux (all editions)
SQL Server 2019 on Windows (all editions)
SQL Server 2019 on Linux (all editions)
Affected releases:
build lower than 15.0.4365.2
Fixed releases:
15.0.4365.2
Description:
Symptoms
Assume that you have an Always On availability group (AG) in an instance of Microsoft SQL Server 2019, Microsoft SQL Server 2017, or Microsoft SQL Server 2016. When you back up a secondary replica that is running in asynchronous-commit mode, the backup operation fails occasionally. Additionally, you might receive the following error message: Error: 9003, Severity: 20, State: 1. The log scan number (nnn:nnn:nnn) passed to log scan in database '<DatabaseName>' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
Resolution
This problem is fixed in the following cumulative updates for SQL Server: Cumulative Update 26 for SQL Server 2019 Cumulative Update 13 for SQL Server 2017 Cumulative Update 4 for SQL Server 2016 Service Pack 2 Cumulative Update 11 for SQL Server 2016 Service Pack 1 About cumulative updates 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: Latest cumulative update for SQL Server 2019 Latest cumulative update for SQL Server 2017 Latest cumulative update for SQL Server 2016
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.
