SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Mirror disconnected


Mirror disconnected

Author
Message
Akkare
Akkare
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1090 Visits: 459
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
Robert Murphy UK1
Robert Murphy UK1
Say Hey Kid
Say Hey Kid (707 reputation)Say Hey Kid (707 reputation)Say Hey Kid (707 reputation)Say Hey Kid (707 reputation)Say Hey Kid (707 reputation)Say Hey Kid (707 reputation)Say Hey Kid (707 reputation)Say Hey Kid (707 reputation)

Group: General Forum Members
Points: 707 Visits: 237
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
Geoff A
Geoff A
SSCarpal Tunnel
SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)

Group: General Forum Members
Points: 4854 Visits: 1828
this is more than likely a DNS issue.

trouble shoot by using ping or nslookup on the witness and make sure they both resolve.
cherish.j.wang
cherish.j.wang
Old Hand
Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)

Group: General Forum Members
Points: 332 Visits: 211
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!
antonio-303614
antonio-303614
Grasshopper
Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)

Group: General Forum Members
Points: 19 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!
Robert Davis
Robert Davis
SSChampion
SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)

Group: General Forum Members
Points: 11797 Visits: 1664
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
SQL Server Best Practices: SQL Server Best Practices
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring
Microsoft Certified Master: SQL Server, Data Platform MVP
Database Engineer at BlueMountain Capital Management
cherish.j.wang
cherish.j.wang
Old Hand
Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)

Group: General Forum Members
Points: 332 Visits: 211
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.;-)
cherish.j.wang
cherish.j.wang
Old Hand
Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)

Group: General Forum Members
Points: 332 Visits: 211
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.;-)
kapfundestanley
kapfundestanley
SSCrazy
SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)

Group: General Forum Members
Points: 2733 Visits: 1320
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
Fraggle-805517
Fraggle-805517
SSCarpal Tunnel
SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)

Group: General Forum Members
Points: 4057 Visits: 1512
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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum







































































































































































SQLServerCentral


Search