This content has been marked as final. Show 6 replies
If you don't run the referential integrity plugin on each master you risk missing the removal of anr references when you remove an entry on a machine without the plugin enabled.
You either need it enabled on all masters or none -- and if none, you must take care of removing references to a deleted entry yourself.
Its probably also worth mentioning that you can only have FOUR masters total in any replication system which includes one or more DS5.2 instances.
Sounds like you have six.
Well - here is the setup, let me know if this is not recommendable :
Server 1 ( 11G ) > Server 3 ( 5.2 )
Server 1 ( 11G ) > Server 5 ( 5.2 )
Server 2 ( 11G ) > Server 4 ( 5.2 )
Server 2 ( 11G ) > Server 6 ( 5.2 )
All the above are master to master, also Server 1 and Server 2 are in master setup as well. does this still exceed number of masters limitation?
To determine if you are exceeding the limit, simply look at all the interconnected systems and count the masters.
If in the entire system, there are more than 4 there are too many.
Its not how many masters are directly connected to each other, its how many masters are connected at all, even indirectly.
There is no hard limit on masters in DS5.2, but testing showed that there was the possibility of fairly severe performance issues with too many masters.
The more masters you have, and the longer you run with >4 masters, the more likely you are to run into performance issues. No guarantee that you will, its just a possibility.
The biggest downside is that configurations with > 4 masters are not supported, so any issues and you call Oracle for support, they may just tell you its an unsupported configuration.