On Thu, 24 Oct 2013, Robert Minsk wrote: > A summary of what I posted below . I have several subordinate databases > and each subordinate database acquires there data via a refreshOnly > syncrepl. Instead of storing the contextCSN on the subordinate database > the contextCSN gets stored on the superior database. As a result the > superior databases contextCSN is the maximum of the subordinate > databases. This causes all but the syncprov server with the latest > contextCSN to abort the sync with "consumer state is newer than > provider!" > > It seems a configuration option needs to be added that allows storing > and reading of the contextCSN on the subordinate databases as well as > the maximum contextCSN on the superior database.
Sounds like you're looking for "sync_use_subentry true", to be used in the database contexts of the consumers. Philip Guenther
