Re: Error: CSN too old and replication fails

[Jérémy Wagner <jeremy.wagner@unistra.fr>]

Le 17/02/2011 00:59, Howard Chu a écrit :
> Your current configuration is unsupported. Ordinarily when you 
> configure multiple consumers in a DB it is assumed they are all 
> pointing at different providers, and each provider will have a 
> different serverID. In your case, since it is all a single provider 
> with a single serverID, all 3 consumers will share a single 
> contextCSN. Any update in any branch will update the contextCSN to 
> that newest state. Any updates in other branches that hadn't been 
> received yet (due to random timing between threads) will be received 
> as "too old" because the contextCSN already has a newer state.
>
> A workaround for this would be to split each consumer into its own 
> subordinate database, then each will have a private copy of its own 
> contextCSN to work with.

Thank you for your answer, it was very helpful.

I followed your advice and configured several databases (one for each 
replicated branch) and it resolved all my replication problems :-)