July 18, 2017 at 7:09 am
Per the Microsoft article : https://support.microsoft.com/en-us/help/3057876/fix-alwayson-database-on-a-secondary-replica-shows-a-not-synchronizing, the issue happens in SQL Server 2014 and they suggest to apply SP1 to fix this.
However I see the same issue in my environment which has SQL 2016 with Sp1.
Any thoughts how to fix this? I don't want to see the repetitive issue occurring every time in the error log.
Thanks.
July 20, 2017 at 7:56 am
SQL-DBA-01 - Tuesday, July 18, 2017 7:09 AMPer the Microsoft article : https://support.microsoft.com/en-us/help/3057876/fix-alwayson-database-on-a-secondary-replica-shows-a-not-synchronizing, the issue happens in SQL Server 2014 and they suggest to apply SP1 to fix this.However I see the same issue in my environment which has SQL 2016 with Sp1.
Any thoughts how to fix this? I don't want to see the repetitive issue occurring every time in the error log.
What are the errors in the error log? Usually you have more information in the log which could identify the cause. Did you try resuming with ALTER DATABASE YourDatabase SET HADR RESUME ?
For a list of some of the reasons for the status, refer to this document:
Data synchronization state of some availability database is not healthy
Sue
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply