Article selected from: https://www.cnblogs.com/wangguanguo/p/9296869.html content
First, create an availability group
Using the SSMs Create Availability Group wizard, add a primary replica node1, one secondary replica node3, and the last step to complete the error:
1 |
无法对可用性组 "XXXXX" 创建、联接或添加副本,因为节点“node3”是副本“node1”和 "node3" 的可能所有者。<br>如果一个副本是故障转移群集实例,请从其可能的所有者中删除重叠的节点,然后再试。(错误:19405) |
Workaround:
1) in the server's failover Cluster Manager, locate the role under the cluster (the 1 position shown in the figure), click on the role to build AlwaysOn (Figure 2), switch to the "Resources" tab, on the server name (3 position in the picture) right-click Properties, in the Pop-up Properties dialog box, select " Advanced Policies tab, you can see that the "Possible Owners" list box lists the node names within the cluster, put the other tick off, and click OK on the Node3 tick.
In the same way, the objects under the "Other resources" and "roles" groups will be node3 from the possible owners.
In this way, theoretically node3 is not a possible owner of Node1 and Node3.
2) Modify the possible owners of the cluster in PowerShell
Run the Get-clusterresource command on the PowerShell command line to view resource within the cluster
Other resources in SQL Server 1 above, use Get-clusterownernode to view possible owners of SQL Server
It is possible that the owner has node1,node2,node3 three nodes, using the cmdlet command to modify the SQL Server Clusterownernode
1 |
Get-ClusterResource -Name "SQL Server" | Set-ClusterOwnerNode -Owners node1,node2 |
where "SQL Server" is the query above the RESOURCE,NODE1,NODE2 is the rest of the cluster inside the node.
Looking again at ownernodes under SQL Server, there is no node3. Modifying other objects in the same way, and then creating the availability group, succeeds.
Reference: https://dba.stackexchange.com/questions/142603/ failed-to-create-join-or-add-replica-to-availability-group-in-sql-server-2014
Category: SQL Server
SQL Server Alwayson build error: 19405