locked
Service and Network RRS feed

  • Question

  • Hi Team,

    Last night we had failover occur from principal to mirror in errorlog it shows below

    The mirroring connection to "TCP://ssss:5022" has timed out for database "xxxx" after 20 seconds without a response.  Check the service and network connections.

    My Question :

    How can we check service and net work connections and how can we prove its net work prob please suggest me.


    subu


    • Edited by subu999 Tuesday, August 6, 2013 5:28 AM
    Tuesday, August 6, 2013 5:05 AM

Answers

  • You can't.  This is a general "cannot ping server for 20 seconds", which causes a failover.

    After the fact there is nothing you can do to prove it was a network error.  The only thing you have is this message.  I assume you did not see any other messages in the Windows event log on the server.

    • Proposed as answer by Sofiya Li Thursday, August 8, 2013 3:36 AM
    • Marked as answer by Sofiya Li Tuesday, August 13, 2013 12:44 PM
    Tuesday, August 6, 2013 5:48 PM

All replies

  • Its may be due to traffic in network at that particular time. Get network statistics history at that particular time.

    To keep a connection open, a server instance must receive a ping on that connection in the time-out period defined, plus the time that is required to send one more ping. Receiving a ping during the time-out period indicates that the connection is still open and that the server instances are communicating over it. On receiving a ping, a server instance resets its time-out counter on that connection.

    If no ping is received on a connection during the time-out period, a server instance considers the connection to have timed out. The server instance closes the timed-out connection and handles the time-out event according to the state and operating mode of the session.

    Even if the other server is actually proceeding correctly, a time-out is considered a failure. If the time-out value for a session is too short for the regular responsiveness of either partner, false failures can occur. A false failure occurs when one server instance successfully contacts another whose response time is so slow that its pings are not received before the time-out period expires.

    In high-performance mode sessions, the time-out period is always 10 seconds. This is generally enough to avoid false failures. In high-safety mode sessions, the default time-out period is 10 seconds, but you can change the duration. To avoid false failures, we recommend that the mirroring time-out period always be 10 seconds or more.

    To change the time-out value (high-safety mode only)

    1.Open your principal database with SQL Server Management Studio.
    2.Open a new SQL query windows and execute the following statement

    ALTER DATABASE yourdatabase SET PARTNER TIMEOUT 30

    To view the current time-out value

    Query mirroring_connection_timeout in sys.database_mirroring.

    Tuesday, August 6, 2013 5:39 PM
  • You can't.  This is a general "cannot ping server for 20 seconds", which causes a failover.

    After the fact there is nothing you can do to prove it was a network error.  The only thing you have is this message.  I assume you did not see any other messages in the Windows event log on the server.

    • Proposed as answer by Sofiya Li Thursday, August 8, 2013 3:36 AM
    • Marked as answer by Sofiya Li Tuesday, August 13, 2013 12:44 PM
    Tuesday, August 6, 2013 5:48 PM