How to avoid "not so Ready to Replicate" conundrums

Chatting with Brett on the yahoo forums has turned up a solution to the not so Ready-to-Replicate problem I posted about previously. It turns out an undocumented setting can disable the R2R feature and allow you to selectively sync back to development servers.

The issue is this: selective section replication works great on a contribution-consumption environment, allowing users to control when sections go live. But how do you replicate those sections back into a test environment? Does it mean that a section has to go live before it can go to test? Definitely not a desirable situation.

I went and checked the 11g documentation (which is much more thorough than the 10g stuff) and there is a way to avoid this issue. The importing server (such as a test environment) can be configured to ignore the R2R flag. Just pop this config variable into the importing server:
SSIgnoreReadyToReplicate=true

Brett confirms that it is backwards-compatible with 10gR4. He also advises that any contribution-consumption model needs the config variable on both servers. You can read our discussion here.