ChannelDB2

Data Replication for Partitioned Databases

This video covers basic data replication considerations for InfoSphere Warehouse and DB2 LUW partitioned databases.

If you're more interested in feeding changed data to a warehouse than you are the partitioned database aspects of InfoSphere Warehouse, see the following developerWorks article:
http://www.ibm.com/developerworks/data/library/techarticle/dm-1007datawarehouse1/index.html

Views: 558

Comment

You need to be a member of ChannelDB2 to add comments!

Join ChannelDB2

Comment by david t on March 24, 2010 at 6:14pm
Hi, Vijay,

Any partition can be the coordinator partition for Q Capture, catalog partition or otherwise. If you have multiple partition servers, your Q Capture can connect to the database through any partition server.

This reminds me that I should have mentioned one recommendation for Q Apply... for best performance, Q Apply should be run on the same system as its DoneMsg table. By default, the DoneMsg table is created in the catalog partition.

thanks
david
Comment by Vijay Bandari on March 23, 2010 at 5:45pm
Hi David,

In case of Remote Capture, the client catloging for the source database, should it be a must to point to the co-ordinator node or to point it to any other node works, in partitioned source environment.

Thanks for simple but clear presentation.

Vijay

Featured Downloads

Try BLU Acceleration on Cloud

© 2017   Created by channeldb2.   Powered by

Badges  |  Report an Issue  |  Terms of Service