Planning for Q Replication

Before configuring replication, plan for key and referential integrity requirements, as well as for storage and initial load of targets.

Choosing the replication key
Replication requires a unique constraint on each table to uniquely identify each row across all databases where the row might be replicated. This is the replication key. The apply program specifies this key is specified in a WHERE clause for updates and deletes to ensure that the correct row is updated.
Considerations for RI constraints
When your tables have referential integrity (RI) constraints, include parent, child, and any other related tables in the same replication set. When adding tables to a replication set, add parent tables first and then the child tables.
Replicating column-organized tables
For better replication performance, you can use column-organized tables instead of row-organized tables.
Workload and database considerations
Because replication uses log-capture/transaction-replay technology on sources and targets that are independent Db2 systems, it requires a few considerations to your workloads and databases.
Data type restrictions
Replication of spatial data types is not supported in IBM® Data Replication for Availability, and some data types can be replicated only under certain circumstances.
Supported DDL operations
IBM Data Replication for Availability supports the following Data Definition Language (DDL) changes:

Parent topic: Q Replication for Continuous Availability