Error: 983, Severity: 14, State: 1;Unable to access availability database 'xxxx' because the database replica is not in the PRIMARY or SECONDARY role.



There is an error occurred on Always On High availability Environment  today. There are two nodes One primary replica and another is Secondary replica. Assume here A is Primary replica and B is a secondary replica. Windows team has a plan to update NET BIOS. So they want do the update on Secondary node(B) which is acting as secondary replica now.  So every database is in Synchronized State in secondary replica(B) because  AG configured as Synchronous Commit.  After NET BIOS update windows team started the services.
Being a DBA, we need to monitor and do the fail over. Once services are started in Secondary replica(B) databases started coming to Synchronized state one by one. There is a database called Orders is taking time as its size is near 1 TB.  After an hour of waiting even this database come to Synchronized state and as usual it Secondary replica now(B) because we hit the secondary replica first.
Now we want to do the same update in Primary replica too(A). So we went to primary replica do the fail over to B(which is acting as  a SECONDARY REPLICA at this moment) and started the fail over and it went smoothly but the when I look at the database status, except Orders  database all other databases came  to Synchronized and B replica is in NOT SYNCHRONIZING state and  even in secondary replica(Now A is secondary  replica) Order database is in NOT SYNCHRONIZING state. In both the  replica B which is acting as Primary now and A which is acting as Secondary now. In  both nodes database is in NOT SYNCHRONIZING state. And  under availability  group side in both the replicas database status is in RED. 
And if I see in error log ( in B server which is acting as Primary  now).  I  found below error.

Error: 983, Severity: 14, State: 1.
2018-09-29 05:32:40.570 Logon 
Unable to access availability database 'DatabaseName' because the database
replica is not in the PRIMARY or SECONDARY role. Connections to an availability database is permitted only
when the database replica is in the PRIMARY or SECONDARY role.

Solution: And I run the below  command to bring this database online state in Primary replica(B which is acting  now)

USE  master
GO
ALTER DATABASE  DatabaseName
SET ONLINE

Comments

Post a Comment

Popular posts from this blog

System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out

I got this error in one of my client's production environment, this type of issues might come up when we are not properly updating statistics. System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out Workaround: Please run UPDATE STATISTICS command in all the tables on a particular database EXEC sp_updatestats So in my scenario UPDATE STATISTICS on all the tables resolved the issue.
Read more

Pre login Handshake or Connection Timeout Period

Image
Service was unable to open new database connection when requested. SqlException: Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  This could be because the pre-login handshake failed or the server was unable to respond back in time.  The duration spent while attempting to connect to this server was - [Pre-Login] initialization=16225; handshake=14840; Connection string - Data Source=sqlserverintancenamehere;Initial Catalog=CatalogNamehere;Integrated Security=True;Persist Security Info=False;Max Pool Size=1000;Connect Timeout=20;Load Balance Timeout=120;Packet Size=4096;Application Name=Applicationname hereBusinessLayerHost.exe;Workstation ID=HostnameHere setspn -a MSSQLSvc/hostname.doaminname.net:1433 ServiceAccountNameHere need to run the above command in a command prompt, most of the time you would NOT have permissions to run this, please check with Active Directory Team or Wi...
Read more

Transparent Data Encryption(TDE) with Master Key and Certificate in SQL Server

Image
/*  There is only one master key, you can not create  multiple */ use master go CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'StrongPasswordHere' GO /*  Creating certificate in the master database, after creating  master key */ use master GO CREATE CERTIFICATE MyFirstCert WITH SUBJECT = 'TDECertificate' ; GO /* Enable databse encryption key but you can not see under this specific user database. */ USE G GO CREATE DATABASE ENCRYPTION KEY WITH ALGORITHM = AES_128 ENCRYPTION BY SERVER CERTIFICATE MyFirstCert GO ALTER DATABASE G SET ENCRYPTION ON;  /*  Backing up certificate */ use master go BACKUP CERTIFICATE MyFirstCert TO FILE = 'C:\Certificates\MyFirstCert' WITH PRIVATE KEY ( FILE = 'C:\Certificates\MyFirstCertKey' , ENCRYPTION ...
Read more