Symptoms
When you run several non-file-growth operations such as backup in Microsoft SQL Server 2014, 2016, or 2017, the operations may use up all the disk space, and there is no sufficient space for critical log growth. Because the database cannot create more log space, database modifications and synchronization with secondaries fail, recovery fails, and the database cannot be brought online. Additionally, you may receive one or more of the following error messages:
-
Error 9002, Severity: 17, State: 9.
The transaction log for database 'DatabaseName' is full due to 'AVAILABILITY_REPLICA' -
Warning 3052: Msg 3052, Level 16, State 1, Line LineNumber
BACKUP LOG was unable to log updates for database 'DatabaseName'.
Subsequent log backups will be required to advance the backup point from 'LSNID1' to 'LSNID2' after log space is made available for logging them. -
Error 3314
During undoing of a logged operation in database 'DatabaseName', an error occurred at log record ID %S_LSN. Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Resolution
This fix is included in the following cumulative updates for SQL Server:
Cumulative Update 1 for SQL Server 2016 SP2
Cumulative Update 5 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 Service 2017
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.
