OPERATIONAL DEFECT DATABASE
...
...
BugZero found this defect 1483 days ago.
Assume that you have an Always On Availability Group (AG) that has only a primary replica (no secondary replicas). Over time, you may encounter the following error message: Error 9002. The transaction log for database is full due to 'AVAILABILITY_REPLICA'. When you run a transaction log backup, the error won't be resolved because the log is not truncated, and it uses all the available space.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem is fixed in the following cumulative updates for SQL Server: Cumulative Update 1 for SQL Server 2019 Cumulative Update 18 for SQL Server 2017 Cumulative Update 10 for SQL Server 2016 SP2 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 2019 Latest cumulative update for SQL Server 2017 Latest cumulative update for SQL Server 2016
This problem is fixed in the following service pack for SQL Server: Service Pack 3 for SQL Server 2016
Learn about the terminology that Microsoft uses to describe software updates.
6
Fixes an issue in which database striped backups using virtual device interface (VDI) tools might fail to restore with error 3456.6
Fixes an issue in which the full-text auto crawl monitor is aborted when you use full-text search.6
Fixes an issue in which the SQL Server Volume Shadow Copy Service (VSS) Writer can't freeze the database during a VSS-based backup. For more information, see known issue three of SQL Server 2019 CU28.6
Fixes an issue in which Data Analysis Expressions (DAX) queries that use SUMMARIZECOLUMNS and ROLLUPGROUP with multidimensional models might produce incorrect results when running multiple queries that have different sub-selects without clearing the cache, which causes inaccurate totals starting from the second query.6
Fixes a contention issue with high KTM_RECOVERY_MANAGER wait times that you might encounter when running XA distributed transactions. Note: You need to turn on trace flag 8531 as a startup trace flag.6
Fixes an issue in which database striped backups using virtual device interface (VDI) tools might fail to restore with error 3456.6
Fixes an issue in which the full-text auto crawl monitor is aborted when you use full-text search.6
Fixes an issue in which the SQL Server Volume Shadow Copy Service (VSS) Writer can't freeze the database during a VSS-based backup. For more information, see known issue three of SQL Server 2019 CU28.6
Fixes an issue in which Data Analysis Expressions (DAX) queries that use SUMMARIZECOLUMNS and ROLLUPGROUP with multidimensional models might produce incorrect results when running multiple queries that have different sub-selects without clearing the cache, which causes inaccurate totals starting from the second query.6
Fixes a contention issue with high KTM_RECOVERY_MANAGER wait times that you might encounter when running XA distributed transactions. Note: You need to turn on trace flag 8531 as a startup trace flag.7.15
Limits the extra number of user tokens created by sys.sysprocesses or sys.dm_exec_requests by using trace flag 4673.7.15
Fixes an issue in the lock manager that might cause random access violations and dumps on secondary replicas when the primary replica has 16 or more processors, and the secondary replicas have less than 16 processors.7.15
Fixes an assertion failure (Location: setypes.cpp:1274; Expression: !IsInRowDiff()) that you might encounter at FAILED_ASSERTION_42ac_sqlmin.dll!VersionRecPtr::IsNull when you have multiple nested inserts. Note: You can enable trace flag (TF) 7117 to mitigate the issue. Turn off TF 7117 after the mitigation is done, which means after the version cleaner cleans the problematic page.7.15
Fixes an assertion failure (Location: setypes.cpp:1274; Expression: !IsInRowDiff()) that you might encounter at FAILED_ASSERTION_42ac_sqlmin.dll!VersionRecPtr::IsNull when you have multiple nested inserts. Note: You can enable trace flag (TF) 7117 to mitigate the issue. Turn off TF 7117 after the mitigation is done, which means after the version cleaner cleans the problematic page.7.15
Fixes an overflow issue of the word occurrence that you encounter during the full-text merging process.
