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

Mirroring - Intermittent "network name is no longer available" Expand / Collapse
Author
Message
Posted Monday, September 09, 2013 1:41 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, April 07, 2014 2:22 PM
Points: 35, Visits: 171
Is this a network issue?

I have a mirroring setup - synchronous with automatic failover. The databases went into Disconnected mode for about a minute last night, and everything was synchronized soon after. Looking at the error logs, the principal server could not contact the secondary server. The secondary server could not contact the witness. But I don't see a message that the principal lost contact with the witness.

There weren't any index defrag jobs running, or heavy activity at the time. This is the first time the issue has happened around that time of day.

Principal error log
12:04:06 AM Database mirroring connection error 4 '64(The specified network name is no longer available.)' for 'TCP://prod02.dg.com:5023'.
12:04:27 AM Database mirroring connection error 2 'Connection attempt failed with error: '10060(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)'.' for 'TCP://prod02.dg.com:5023'.

Secondary error log
12:03:46 AM Database mirroring connection error 4 'An error occurred while receiving data: '64(The specified network name is no longer available.)'.' for 'TCP://PROD-WITNESS.dg.com:5024'.
12:03:46 AM Database mirroring connection error 4 '10054(An existing connection was forcibly closed by the remote host.)' for 'TCP://prod01.dg.com:5022'.

I am responsible for doing a root cause analysis, and am in a DBA role. Does this look like a network issue? If so, is there anything I can suggest that my IT department look into to pinpoint the problem? We've had similar issues intermittently, and they haven't found anything. We use VMWare.

How can I tell if there was a loss of quorum in a mirroring session? There were application timeout errors, and trying to determine whether these were due to the mirroring issues, or just the network. Any thoughts you have would be appreciated.

Thanks!
Dan
Post #1492909
Posted Monday, September 09, 2013 1:46 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: 2 days ago @ 6:58 AM
Points: 1,242, Visits: 1,385
We just experienced a long period of network performance issues that resulted in a lot of those same errors in SQL backups. The root cause was a bad drive in the SAN.
Post #1492911
Posted Monday, September 16, 2013 8:17 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, April 07, 2014 2:22 PM
Points: 35, Visits: 171
Thanks for your response. I will keep that in mind.
Post #1495108
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse