Hi,
I am in a weird situation. I have a Distributed AG setup between London and Flint servers(2 London and 2 Flint). London is the global primary and Flint is the global secondary). I did the rolling upgrade on these servers. After the upgrade, manual failover of the Forwarder to its Secondary(on which Distributed AG was created) fails while regular Ags are not showing this behavior.
I have set Sync mode to SYNCHRONOUS COMMIT and failover mode to MANUAL. As soon as I change failover mode to AUTOMATIC, DAG can failover. Issue is with the MANUAL failover mode.
It shows error which is weird. Databases are SYNCHRONIZED still following error appears:-
ERR [RES] SQL Server Availability Group <xxx>: [hadrag] Failed to execute SQL command to perform the requested operation
ERR [RES] SQL Server Availability Group <xxx>: [hadrag] ODBC Error: [42000] [Microsoft][SQL Server Native Client 11.0][SQL Server]The availability replica for availability group 'xxxx' on this instance of SQL Server cannot become the primary
replica. One or more databases are not synchronized or have not joined the availability group. If the availability replica uses the asynchronous-commit mode, consider performing a forced manual failover (with possible
ERR [RES] SQL Server Availability Group <xxx>: [hadrag] data loss). Otherwise, once all local secondary databases are joined and synchronized, you can perform a planned manual failover to this secondary replica (without data loss). For more
information, see SQL Server Books Online. (41142)
ERR [RES] SQL Server Availability Group <xxx>: [hadrag] Failed to execute availability group command stored procedure
INFO [RES] SQL Server Availability Group <xxx>: [hadrag] Disconnect from SQL Server
Please suggest what is wrong.
P.S. This behavior was not there when it was SQL SERVER 2016. It started happening only after upgrade to SQL SERVER 2017. Additionally, regular AGs on those servers are not causing any problem.
ravinder1483@gmail.com