Common restrictions for JDBC data sources

Common constraints

• If the structure of a data source table is changed with either an ALTER TABLE or a DELETE TABLE and a CREATE TABLE statement, follow these steps:
  1. Remove the table from all subscriptions.
  2. Execute the ALTER TABLE or the DELETE TABLE and the CREATE TABLE statement.
  3. Add the table back to the subscriptions.

  The reason for these steps is to ensure that the source capture triggers remain operable. For example, DB2 renders triggers inoperable upon the execution of any ALTER TABLE or DELETE TABLE statement.

Referential-integrity (RI) constraints

If your source tables have RI constraints, observe the following restrictions to avoid synchronization and replication failures due to RI constrain violations:

• Do not update the primary keys on the client database or mobile device.
• Do not subscribe tables that have parent-child relationships which involve cycles (for example self-loops).
• Tables must be added in parent-to-child order during subscription creation.
• RI relationships cannot cross any subscription boundaries.
• Do not subscribe tables that have triggers.