In this scenario, you restart the SQL Server instance hosting the primary replica of the availability group. You review the sys.dm_exec_requests DMV and notice the DB STARTUP command is blocked on wait HADR_RECOVERY_WAIT_FOR_UNDO. The databases indicate the "Not Synchronizing" status. For example, the primary replica is upgraded to SQL Server 2019 CU21, and the secondary replica remains SQL Server 2019 CU19. You upgrade a replica to this cumulative update. The databases use memory-optimized tables, the FileStream class, or multiple log files. Assume that the databases of an Always On availability group have one of the following conditions: This issue is caused by a change introduced in SQL Server 2019 CU20 for the Managed Instance link feature. Microsoft is working on a fix for this issue and it will be available in a future CU. To do this, use the following trace flags:ġ1042 - This trace flag disables the parallelism for the built-in SESSION_CONTEXT.ĩ432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in SESSION_CONTEXT. However, this fix might create access violation dump files when the SESSION is reset for reuse. SQL Server 2019 CU14 introduced a fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT. This update contains 28 fixes that were issued after the release of SQL Server 2019 Cumulative Update 20, and it updates components in the following builds: This article describes Cumulative Update package 21 (CU21) for Microsoft SQL Server 2019.
0 Comments
Leave a Reply. |