Skip to content

Commit 7ac2cef

Browse files
author
Simonx Xu
authored
Merge pull request #4891 from MonicaChenc/monicasql2019cu21
Update 2347043 in SQL Server 2019 CU21
2 parents 775c783 + 77f2157 commit 7ac2cef

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

support/sql/releases/sqlserver-2019/cumulativeupdate21.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Cumulative update 21 for SQL Server 2019 (KB5025808)
33
description: This article contains the summary, known issues, improvements, fixes and other information for SQL Server 2019 cumulative update 21 (KB5025808).
4-
ms.date: 07/03/2023
4+
ms.date: 09/05/2023
55
ms.custom: KB5025808
66
ms.reviewer: v-qianli2
77
appliesto:
@@ -85,7 +85,7 @@ For more information about the bugs that are fixed and enhancements that are inc
8585
| <a id="2195940">[2195940](#2195940)</a> | Fixes an issue where messages in the `sys.transmission_queue` of the initiator database in a SQL Server Service Broker conversation are missing or stuck after a failover of the target database.| SQL Server Engine | High Availability and Disaster Recovery | All |
8686
| <a id="2101590">[2101590](#2101590)</a> | Fixes an issue where restoring an In-Memory OLTP database backup that has Transparent data encryption (TDE) enabled fails and returns the following error message: </br></br>Error: 33126, Severity: 16, State: 1. </br>Database encryption key is corrupted and cannot be read. </br></br>**Note**: To apply this fix, you need to enable a trace flag (TF) to relax TDE checks for In-Memory tables and disable the TF after the restoration is completed. For more information, contact [Microsoft Customer Service and Support](https://support.microsoft.com/contactus/?ws=support). | SQL Server Engine | In-Memory OLTP | Windows |
8787
| <a id="2184943">[2184943](#2184943)</a> | Fixes an assertion dump issue (Location: "sql\\\ntdbms\\\hekaton\\\engine\\\core\\\tx.cpp":4753; Expression: 0 == Dependencies.CommitDepCountOut) that causes an availability group failover. | SQL Server Engine | In-Memory OLTP | All |
88-
| <a id="2347043">[2347043](#2347043)</a> | Fixes the following error that you may encounter when you try to restore a database and the checkpoint file is corrupted: </br></br>[ERROR] Recovery failed with error 0x84000004 on database 10. This error will be mapped to 'HK_E_RESTORE_ABORTED' (0x82000018). (sql\ntdbms\hekaton\runtime\src\hkruntime.cpp : 5051 - 'HkRtRestoreDatabase') | SQL Server Engine | In-Memory OLTP | Windows |
88+
| <a id="2347043">[2347043](#2347043)</a> | Provides the details of the corrupt checkpoint file that's associated with the in-memory database when you try to restore a database but it fails with the following error: </br></br>[ERROR] Recovery failed with error 0x84000004 on database 10. This error will be mapped to 'HK_E_RESTORE_ABORTED' (0x82000018). (sql\ntdbms\hekaton\runtime\src\hkruntime.cpp : 5051 - 'HkRtRestoreDatabase') | SQL Server Engine | In-Memory OLTP | Windows |
8989
| <a id="2401115">[2401115](#2401115)</a> | Fixes a dump issue where a huge number of concurrent In-Memory OLTP transactions cause a stack overflow. | SQL Server Engine | In-Memory OLTP | All |
9090
| <a id="2404944">[2404944](#2404944)</a> | Removes the need for running the `sys.sp_xtp_force_gc` stored procedure twice to free up allocated and used XTP memory, and running it once is enough. You need at least the `ALTER SERVER STATE` permission to run this procedure. | SQL Server Engine | In-Memory OLTP | All |
9191
| <a id="2312800">[2312800](#2312800)</a> | Fixes an issue where external data sources that use the generic ODBC connector may not work after you install SQL Server 2019 CU19 or later versions. You may encounter the following scenarios: </br></br>- When you try to query an external table that was created before you install this fix on a generic ODBC data source, and the `CONNECTION_OPTIONS` argument uses a `DSN` parameter without the `Driver` keyword, you receive the following error message: </br></br>Msg 7320, Level 16, State 110, Line \<LineNumber> </br>Cannot execute the query "Remote Query" against OLE DB provider "MSOLEDBSQL" for linked server "(null)". Object reference not set to an instance of an object. </br></br>- If you try to create a new external table, you receive the following error message: </br></br>Msg 110813, Level 16, State 1, Line \<LineNumber> </br>Object reference not set to an instance of an object. </br></br>**Note**: Before you apply this fix, you can uninstall SQL Server 2019 CU19 or later versions, or add the `Driver` keyword to the `CONNECTION_OPTIONS` argument as a workaround. For more information, see [Generic ODBC external data sources may not work after installing Cumulative Update](https://techcommunity.microsoft.com/t5/sql-server-support-blog/generic-odbc-external-data-sources-may-not-work-after-installing/ba-p/3783873). | SQL Server Engine | PolyBase | Windows |

0 commit comments

Comments
 (0)