November 26, 2015 at 4:08 am
Hello,
I have a issue on AlwaysOn Group two nodes (SQL 2014 SP1 - Windows 2012 R2 Datacenter).
I have some databases on secondary with a statut 'not synchronized'. Ok I tried to remove the database from Availability group without any problem but normally when you did that the database on secondary becomes in restoring mode. The database still kept the statut 'not synchronized'. Well the problem now I can't delete the database on secondary !!
Error: 35220, Severity: 16, Could not process the operation. AlwaysOn Availability Groups replica manager is waiting for the host computer to start a Windows Server Failover Clustering (WSFC) cluster and join it. Either the local computer is not a cluster node, or the local cluster
Do you have a solution to drop the secondary ?
Thanks for your help,
Eric
November 26, 2015 at 7:11 am
Just to addind some informations.
I tried to restart SQL Engine and I can't stop it because there're some phantom's transactions (see picture).
I tried to kill them but nothing happen.
Thanks
November 26, 2015 at 7:32 am
Have you tried recovering the secondary, then putting it into restricted_user mode first? (Sorry- I had a similar issue recently, but without the instances actually in front of me it's hard to diagnose.)
Edit: obviously you need to fix the cluster issue too.
November 26, 2015 at 8:21 am
You need to kill those session which are trying to connect to your replica.
and then try to drop it.
or
kill those session and restore database with recovery and then drop it.
November 26, 2015 at 9:05 am
Hi,
What do you mean by "recovering the secondary" ?
I have 80 databases on default instance only three of them are in "not synchronizing".
Regards,
Eric
November 26, 2015 at 9:10 am
Hi,
I tried to kill session but nothing happen. I still have the session up implicated (. I tried to reboot to IIS server (DI2032SW) but the session SPID 242 doesn't disappear.
Regards,
Eric
November 26, 2015 at 9:55 am
go into failover cluster manager and check that the cluster role for the AO group has started.
Post a screenshot of the failover cluster manager view if you're unsure
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 26, 2015 at 11:00 am
Hi,
The cluster rôle AO looks like good.
On the AO Dashboard, DI2097SW server (secondary) said replica is disconnected. When I connected to it, only one database is not synchronizing.
I don't understand something. I removed two of databases with statut not synchronizing from AO with success but when I checked the secondary these databases have been a statut "not synchronizing" normally the right statut should "restoring". It's looks like something broken but I don't how I can fix it.
I tried to stop sql engine on secondery but stop is pending. WHen I checked SQL log nonqualified transactions are being rolled back in Urgences Database. I think this is the reason why I can't stop sql engine.
Hope I'm clear.
Thanks for your help.
Eric
November 26, 2015 at 3:59 pm
alter database <Database name> set hadr off
what error are you seeing in event viewer ? related to windows cluster ?
November 26, 2015 at 9:27 pm
Change directory to the server instance and use the Remove-SqlAvailabilityDatabase cmdlet
Remove-SqlAvailabilityDatabase `
-Path SQLSERVER:\Sql\SecondaryComputer\InstanceName\AvailabilityGroups\MyAg\Databases\MyDb8
November 27, 2015 at 3:56 am
I executed on secondary the following command : ALTER DATABASE ZEPRA SET HADR OFF and get this error message.
Error: 35220, Severity: 16, Could not process the operation. AlwaysOn Availability Groups replica manager is waiting for the host computer to start a Windows Server Failover Clustering (WSFC) cluster and join it. Either the local computer is not a cluster node, or the local cluster.
Thanks,
Eric
November 27, 2015 at 4:00 am
ERIC CRUDELI (11/27/2015)
Error: 35220, Severity: 16, Could not process the operation. AlwaysOn Availability Groups replica manager is waiting for the host computer to start a Windows Server Failover Clustering (WSFC) cluster and join it. Either the local computer is not a cluster node, or the local cluster.Thanks,
Eric
Check the cluster service is running on this node.
It would also be wise to perform a full cluster validation and check the results
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 27, 2015 at 6:30 am
Hi,
The cluster service on each Node is started.
Regards,
Eric
November 27, 2015 at 7:05 am
ERIC CRUDELI (11/27/2015)
Hi,The cluster service on each Node is started.
Regards,
Eric
Run a cluster validation and check the report
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 27, 2015 at 2:36 pm
Somehow your secondary is not part of cluster node that what it look like from snapshot you have uploaded.
Please make sure it is part of cluster.
Just check in event viewer critical error in windows error log. and upload here.
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply