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 Error 1479, 1474 Expand / Collapse
Author
Message
Posted Wednesday, September 12, 2012 2:09 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 5:56 AM
Points: 1,068, Visits: 3,033
Hi,

OS - win 2008 R2 x64 enterprise edition
SQL - MSSQL R2 x64 enterprise edition with sp2

Pl. suggestion me, how to avoid these erroe in feature? are they required to apply any patch in sql side?

But, I am not enable any threshold like unsent log, unrestore log, commit overhead etc.. now its running system default values.


Principal server
-----------------

Message
Error: 1479, Severity: 16, State: 2.

Message
The mirroring connection to "TCP://servername:5023" has timed out for database "dbname" after 10 seconds without a response. Check the service and network connections.


Mirror server
-------------
source spid21s

Message
Error: 1474, Severity: 16, State: 1.


Message
Database mirroring connection error 4 'An error occurred while receiving data: '10054(An existing connection was forcibly closed by the remote host.)'.' for 'TCP://servername:5022'.

Post #1357831
Posted Wednesday, September 12, 2012 3:04 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 10:36 AM
Points: 6,466, Visits: 13,920
are you using the default mirroring timeout value?

What is the result of the following query?

select mirroring_connection_timeout from sys.database_mirroring



-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1357845
Posted Wednesday, September 12, 2012 3:10 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 5:56 AM
Points: 1,068, Visits: 3,033
Perry Whittle (9/12/2012)
are you using the default mirroring timeout value?

What is the result of the following query?

select mirroring_connection_timeout from sys.database_mirroring



Yes, currently default mirroring time out values.

query result
mirroring_connection_timeout = 10

Post #1357847
Posted Wednesday, September 12, 2012 3:42 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 5:56 AM
Points: 1,068, Visits: 3,033
I assume that DB Mirror environment is configured such a way that it utilizes synchronous mirroring without automatic failover and no wittness.

If the Mirrorred instance doesnt not receive any responses to Ping for 10 seconds from Principal and mirror server.

Pl. confirm, should I change this default value? at principal server end

ALTER DATABASE <dbname> SET PARTNER TIMEOUT 60





Post #1357864
Posted Wednesday, September 12, 2012 4:52 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 10:36 AM
Points: 6,466, Visits: 13,920
it needs to account for network latency so yes change it to whatever you require

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1357885
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse