Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Mirror disconnected Expand / Collapse
Author
Message
Posted Tuesday, January 17, 2012 8:32 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, July 1, 2014 1:08 AM
Points: 102, Visits: 416
I have sql server 2008 on windows 2008
Mirror configured with Witness(Certificate authentication)
today I found that Mirror disconnected state.I got the below error on SQL Error log on primary server

Database mirroring connection error 4 'An error occurred while receiving data: '64(The specified network name is no longer available.)'.' for 'TCP://wedcb469:5023'.
2012-01-17 02:04:01.090 spid20s Error: 1474, Severity: 16, State: 1.

I am able to connect Primary ,Witness and Mirror servers from all 3 servers

but still mirror is in disconnected state.

I found one more error on errorlog.

An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '')

can somebody help me on this
Post #1237273
Posted Tuesday, January 17, 2012 8:43 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, February 22, 2013 7:38 AM
Points: 283, Visits: 226
Can you resume the mirroring session? A network outage of more than (x) minutes will put the session into a suspended state. I dont know what the value of x is, but I have experienced this issue many times.



ALTER DATABASE <database_name> SET PARTNER RESUME



Robert Murphy, Microsoft MCITP (Database Administrator 2008) and MCAD Certified
Post #1237280
Posted Tuesday, January 17, 2012 2:37 PM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Tuesday, October 7, 2014 6:08 AM
Points: 514, Visits: 1,735
this is more than likely a DNS issue.

trouble shoot by using ping or nslookup on the witness and make sure they both resolve.
Post #1237545
Posted Monday, January 23, 2012 12:46 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, September 15, 2014 4:01 PM
Points: 19, Visits: 159
Recently days, I have encountered the same issue of my production SQL Server 2008 database mirror and I fixed it as following:
on the mirror server
use master
GO
alter endpoint endpoint_name state = stopped;
GO
alter endpoint endpoint_name state = started;
GO

may you success!
Post #1240016
Posted Tuesday, June 19, 2012 9:05 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, February 10, 2014 5:42 AM
Points: 1, Visits: 34
cherish.j.wang (1/23/2012)
Recently days, I have encountered the same issue of my production SQL Server 2008 database mirror and I fixed it as following:
on the mirror server
use master
GO
alter endpoint endpoint_name state = stopped;
GO
alter endpoint endpoint_name state = started;
GO

may you success!


Nice one, it works fine!! Thanks a lot!
Post #1318106
Posted Wednesday, June 20, 2012 9:02 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, October 13, 2014 4:42 PM
Points: 1,618, Visits: 1,549
You are less likely to have a name resolution problem if you use the fully qualified domain name of the servers. Name resolution is probably the root cause of the issue. Then you encountered a "poisoned queue" issue. Mirroring is built on top of the service broker engine, and too many consecutive errors will cause the queue behind the endpoint to shut down (the endpoint is still running, but the queue behind it is not).

cherish.j.wang showed you how to get the queue to start up again, but the root cause may still need to be addressed.




My blog: SQL Soldier
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring
Microsoft Certified Master: SQL Server 2008
Principal DBA: Outerwall, Inc.
Also available for consulting: SQL DBA Master
Post #1318786
Posted Thursday, June 21, 2012 8:36 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, September 15, 2014 4:01 PM
Points: 19, Visits: 159
Robert Davis (6/20/2012)
You are less likely to have a name resolution problem if you use the fully qualified domain name of the servers. Name resolution is probably the root cause of the issue. Then you encountered a "poisoned queue" issue. Mirroring is built on top of the service broker engine, and too many consecutive errors will cause the queue behind the endpoint to shut down (the endpoint is still running, but the queue behind it is not).

cherish.j.wang showed you how to get the queue to start up again, but the root cause may still need to be addressed.


Robert is correctly. I don't the root cause yet. I have came across this issue of mirroring many time and fixed it via restart endpoint already.
Post #1319346
Posted Thursday, June 21, 2012 8:44 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, September 15, 2014 4:01 PM
Points: 19, Visits: 159
Robert Davis (6/20/2012)
You are less likely to have a name resolution problem if you use the fully qualified domain name of the servers. Name resolution is probably the root cause of the issue. Then you encountered a "poisoned queue" issue. Mirroring is built on top of the service broker engine, and too many consecutive errors will cause the queue behind the endpoint to shut down (the endpoint is still running, but the queue behind it is not).

cherish.j.wang showed you how to get the queue to start up again, but the root cause may still need to be addressed.


Robert is correctly. I don't the root cause yet. I have came across this issue of mirroring many time and fixed it via restart endpoint already.
Post #1319355
Posted Monday, July 9, 2012 5:24 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, October 10, 2014 5:24 AM
Points: 966, Visits: 1,166
Restarting your DNS will resolve the issue.

“When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris
Post #1326771
Posted Tuesday, July 17, 2012 10:43 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, October 16, 2014 8:54 AM
Points: 727, Visits: 1,424
General question here. Anyone got an idea on how to get alerted/notified/emailed on this. Our server actually went down and we didn't know the witness couldn't see the mirror, so no automatic failover.

Thoughts?

Fraggle
Post #1330885
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse