Amir, Because of the fact that it is hard to sync the transaction logs generated at different nodes for a single transaction (due to the inherent nature of the partitioned table), Replication is allowed only on single node table. But one possible alternative is to consider creating a single node copy for a multi-node table and then using a trigger on the multi-node table to copy data to this signal node table which in turn can be replicated. We have done this successfully in db2 v7. Older version of DB2 capture had some check in there for the source node (even for the trigger based transaction) which will then wont replicate the record originated from a node other than the one where single node table is defined. But it was fixed later and if you are using DB2 v7, you should be fine. Regards, Ajith
-----Original Message----- From: Amir Sadeghi [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 15, 2002 11:54 AM To: [EMAIL PROTECTED] Subject: [DB2EUG] Replication in EEE Hi Team, We are looking to use DB2 replication in order to capture changes in our OLTP system and apply it to our DataWarehouse. We are on EEE with most of the tables partitioned across nodes. I just came across a paragraph in the documentation that indicates this can't be done on EEE unless the table is non-partitioned and on the catalog node. Is this true? What other choices do we have? Thanks in advance. _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
