Hi Ajay, You wrote ...
> Node A will be Master node and all other nodes are remote nodes. The requirement > is that from all remote nodes (B,C,D,E) data should be replicated to the master > node (A). In this case master node A is not going to forward the data to other > remote nodes. If node A does NOT forward data to the other nodes, WHO will? Consider a customer table. Unless the table is horizontally partitioned, so that node A has one segment, B has another segment, etc., and the master node has all four segments, any update to a customer in B *has* to be propagated to all other four nodes, so either B replicates directly to the other four, or it replicates to the master and the master forwards, or some combination thereof. Otherwise the address of some customer will be correct in B and A but not in C, D or E. > So is there any way that will allow me to avoid this extra path from master to > remote node. As I stated earlier, you have to imagine yourself at *each* node and ensure that an update reaches *all* desired targets. I only started to give you the configuration, but as I said you have to have 20 paths when you're done. This is the full configuration for a star, five-node scheme: Orig Local Target 20 20 10 B copies to master 20 10 30 Master sends on to other three 20 10 40 20 10 50 30 30 10 C copies to master 30 10 20 Master sends on to other three 30 10 40 30 10 50 40 40 10 D copies to master 40 10 20 Master sends on to other three 40 10 30 40 10 50 50 50 10 E copies to master 50 10 20 Master sends on to other three 50 10 30 50 10 40 10 10 20 Master propagates to all four 10 10 30 (for completeness) 10 10 40 10 10 50 The last four may never be used but they should still be specified. Regards, Joe Abbate Senior Software Engineer Computer Associates [EMAIL PROTECTED] _______________________________________________ Users mailing list [email protected] http://ingres.ca.com/mailman/listinfo/users
