This section is not applicable to Sybase Replication Agent support
for DB2 Universal Database.
To capture data for replication, the trigger-based Sybase Replication Agent creates insert, update, and delete triggers for each table to be replicated. The triggers are created during the table-marking process.
Child tables subject to being “cascade deleted” when their parent table is deleted cannot have a delete trigger defined. The same problem occurs if you define a cascade delete rule for a table that has a delete trigger defined. Some database servers do not allow cascade delete rules for tables with a delete trigger defined.
The JDBC protocol includes many cascade delete RI rules. To use a trigger-based Sybase Replication Agent, these rules must be dropped for all tables marked for replication.
If cascade delete operations are required in a primary database, then:
The applications (managers) need to delete the child tables first, or
Additional logic must be built into the parent tables' delete triggers to delete the child tables.
