Update 3418490 and the corresponding known issue

MonicaChenc · MonicaChenc · commit 89f963f99e96 · 2025-04-30T09:44:13.000Z
diff --git a/support/sql/releases/includes/patching-error-2019.md b/support/sql/releases/includes/patching-error-2019.md
@@ -1,10 +1,10 @@
 ---
 ms.author: jaferebe
 author: JamesFerebee
-ms.date: 08/20/2024
+ms.date: 04/30/2025
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall, evergreen
 ---
-SQL Server 2019 CU27 introduced fix [2994446](../sqlserver-2019/cumulativeupdate27.md#2994446) to make secondary databases in an availability group (AG) startup more reliably. However, this fix causes a problem where AG databases don't start recovery if SQL Server is running in single-user mode. SQL Server Setup runs in single-user mode. As a result of this, if you run Setup and also have SQL replication, change data capture (CDC), or SQL Server Integration Services database (**SSISDB**) enabled on a database in the AG, when the catalog upgrade scripts try to run but can't access the database, setup fails.
+SQL Server 2019 CU27 introduced fix [2994446](../sqlserver-2019/cumulativeupdate27.md#2994446) to make secondary databases in an availability group (AG) startup more reliably. However, this fix causes a problem where AG databases don't start recovery if SQL Server is running in single-user mode. SQL Server Setup runs in single-user mode. As a result of this, if you run Setup and also have SQL replication or change data capture (CDC) enabled on a database in the AG, when the catalog upgrade scripts try to run but can't access the database, setup fails.
 
 After SQL Server Setup initially fails, the SQL Server service then tries to come online again without single-user mode. At that time, the patch upgrade scripts finish successfully and patching is complete. Once startup completes, the issue is resolved and no user action is required.
 
@@ -22,7 +22,7 @@ If you want to prevent the patch from reporting an initial failure, you can perf
 
 - Enable Trace Flag 12347 - reverts the changes made in fix [2994446](../sqlserver-2019/cumulativeupdate27.md#2994446). You should remove this trace flag after patching.
 
-- Drop the **SSISDB**, CDC, or replication enabled database from the AG.
+- Drop the CDC or replication enabled database from the AG.
 
 - Remove CDC or replication from the database in the AG.
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate27.md b/support/sql/releases/sqlserver-2019/cumulativeupdate27.md
@@ -1,7 +1,7 @@
 ---
 title: Cumulative update 27 for SQL Server 2019 (KB5037331)
 description: This article contains the summary, known issues, improvements, fixes and other information for SQL Server 2019 cumulative update 27 (KB5037331).
-ms.date: 01/29/2025
+ms.date: 04/30/2025
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall, evergreen, KB5037331
 ms.reviewer: v-qianli2
 appliesto:
@@ -33,7 +33,7 @@ This issue is fixed in [SQL Server 2019 CU28](cumulativeupdate28.md#3312461).
 
 [!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
-### Issue three: Patching error for secondary replicas in an availability group with databases enabled replication, CDC, or SSISDB
+### Issue three: Patching error for secondary replicas in an availability group with databases enabled replication or CDC
 
 [!INCLUDE [patching-error-2019](../includes/patching-error-2019.md)]
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate28.md b/support/sql/releases/sqlserver-2019/cumulativeupdate28.md
@@ -1,7 +1,7 @@
 ---
 title: Cumulative update 28 for SQL Server 2019 (KB5039747)
 description: This article contains the summary, known issues, improvements, fixes and other information for SQL Server 2019 cumulative update 28 (KB5039747).
-ms.date: 01/29/2025
+ms.date: 04/30/2025
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall, evergreen, KB5039747
 ms.reviewer: v-qianli2
 appliesto:
@@ -27,7 +27,7 @@ This article describes Cumulative Update package 28 (CU28) for Microsoft SQL Ser
 
 [!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
-### Issue two: Patching error for secondary replicas in an availability group with databases enabled replication, CDC, or SSISDB
+### Issue two: Patching error for secondary replicas in an availability group with databases enabled replication or CDC
 
 [!INCLUDE [patching-error-2019](../includes/patching-error-2019.md)]
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate29.md b/support/sql/releases/sqlserver-2019/cumulativeupdate29.md
@@ -1,7 +1,7 @@
 ---
 title: Cumulative update 29 for SQL Server 2019 (KB5046365)
 description: This article contains the summary, known issues, improvements, fixes and other information for SQL Server 2019 cumulative update 29 (KB5046365).
-ms.date: 10/31/2024
+ms.date: 04/30/2024
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall, evergreen, KB5046365
 ms.reviewer: v-qianli2
 appliesto:
@@ -45,7 +45,7 @@ For more information about the bugs that are fixed and enhancements that are inc
 | <a id=3539961>[3539961](#3539961) </a> | Fixes an issue in which database striped backups using virtual device interface (VDI) tools might fail to restore with [error 3456](../../database-engine/backup-restore/backup-multistriped-vdi-issue.md). | SQL Server Engine| Backup Restore| All |
 | <a id=3287653>[3287653](#3287653) </a> | Fixes an assertion failure (Location: ListenerSpec.cpp:480; Expression: totalUsed + cbListenerName <= cbObj) that you encounter when creating a [distributed availability group (DAG)](/sql/database-engine/availability-groups/windows/distributed-availability-groups) and incorrectly specifying the number of availability groups in it to be other than two. | SQL Server Engine| High Availability and Disaster Recovery | All|
 | <a id=3407955>[3407955](#3407955) </a> | Fixes an issue in which a log backup stops responding on the primary replica after the secondary replica restarts if no additional workloads exist on the primary database. | SQL Server Engine| High Availability and Disaster Recovery | All|
-| <a id=3418490>[3418490](#3418490) </a> | Fixes a patching error that you encounter in secondary replicas of an availability group with databases that have SQL replication, change data capture (CDC), or SQL Server Integration Services database (SSISDB) enabled. For more information, see [known issue two of SQL Server 2019 CU28](cumulativeupdate28.md#issue-two-patching-error-for-secondary-replicas-in-an-availability-group-with-databases-enabled-replication-cdc-or-ssisdb) or [known issue three of SQL Server 2019 CU27](cumulativeupdate27.md#issue-three-patching-error-for-secondary-replicas-in-an-availability-group-with-databases-enabled-replication-cdc-or-ssisdb). | SQL Server Engine| High Availability and Disaster Recovery | Windows|
+| <a id=3418490>[3418490](#3418490) </a> | Fixes a patching error that you encounter in secondary replicas of an availability group with databases that have SQL replication or change data capture (CDC) enabled. For more information, see [known issue two of SQL Server 2019 CU28](cumulativeupdate28.md#issue-two-patching-error-for-secondary-replicas-in-an-availability-group-with-databases-enabled-replication-or-cdc) or [known issue three of SQL Server 2019 CU27](cumulativeupdate27.md#issue-three-patching-error-for-secondary-replicas-in-an-availability-group-with-databases-enabled-replication-or-cdc). | SQL Server Engine| High Availability and Disaster Recovery | Windows|
 | <a id=3336595>[3336595](#3336595) </a> | Adds a validation for the `MODEL` parameter when running `PREDICT` to avoid errors due to the input of wrong models.| SQL Server Engine| Query Execution | All |
 | <a id=3362873>[3362873](#3362873) </a> | Fixes an issue with checkpoint operation in which the following error 2601 occurs when SQL Server tries to perform a checkpoint operation on the database that has change tracking enabled: </br></br>\<DateTime> Error: 2601, Severity: 14, State: 1. </br>\<DateTime> Cannot insert duplicate key row in object '\<ObjectName>' with unique index '\<IndexName>'. The duplicate key value is \<KeyValue>. | SQL Server Engine| Replication | All|
 | <a id=3419782>[3419782](#3419782) </a> | Allows you to disable [OLE DB streaming](/sql/relational-databases/replication/agents/replication-distribution-agent) by passing `-UseOledbStreaming 0` for the Replication Distribution Agent to avoid the error mentioned in [Error message when you run the Distribution Agent in SQL Server](../../database-engine/replication/error-run-distribution-agent.md). | SQL Server Engine| Replication | All|
