Re: Replication Query

> Senario: > Due to a network issue the Primary Server cannot see the Secondary > Server for some time. > Network is establised after some time. > > Observation : > The Replication State in Primary is shown as "off". > The Secondary Server the Replication State is shown as "on". > The informix log in the Secondary Server show : DR: Server state > incompatible > > Problem : Replication is not starting automatically as soon as the > network is up. > > Question : Can the replication start automatically when the Primary > and Secondary can see each other. ( Is there any parameter setting > which is required ? ) > Well, it sounds like the problem is the secondary is not recognizing that the network connection was broken, so HDR is not getting taken down properly when the problem occurs. I believe the DR: Server state incompatible messages in your secondary log are your primary machine attempting to reconnect to the secondary, but since the secondary didn't realize a problem occured, it's causing a problem. One thing you might check is if the TCP keepalive parameter is set the same on both the primary and secondary. I've seen in the past where 1 machine keepalive is set lower so it detects the network problem and generates an error on 1 side of the connection but the other side with the higher value does not. This can cause the type of problem you are describing. But generaly speaking, replication should be able to start automatically, if both sides of the connection realize there is a problem, but in your case it appears as though the secondary is not realizing there is a connection problem.