The parent table is in replication and the child table is not in replication. However, when the child table is dropped on source, the parent table gets dropped from replication and is also dropped on target.
1. Source table tab1 in config.
2. On source: create a table tab2 with a foreign key reference to tab1.
3. drop table tab2
4. This ends up dropping tab1 from replication and issues the command to drop tab1 on the target
Issuing a DDL on a non-replicated child table in the parent-child relationship causes capture to replicate the DDL on the replicated parent table. This happens if there is any IOT table in replication even if the parent/child table is not IOT table.
Issue fixed in version 22.214.171.124 . The latest version of SharePlex for Oracle can be downloaded at: