Constraints

Constraints on the target database can cause conflicts. Especially foreign key constraints with the "delete cascade" feature. This is because if this constraint exists on the source table, then the parent and child rows will be deleted and both deletes will be replicated to the target database. 

Dbvisit Replicate will first delete the parent record on the target database, the constraint will then delete the child record, and then Dbvisit Replicate wants to delete the child record. This will cause a conflict because the child record will not exist anymore.

Unsupported constraints

To check if there are unsupported constraints on the target database, please run the following query:

 ONLY REQUIRED TO RUN AGAINST THE TARGET DATABASE and only if target is ORACLE. Referential integrity constraint check.

 This query may return results, but it is only applicable to schemas and tables that are being replicated.

Prompt ONLY RUN ON TARGET DATABASE!
select owner,
constraint_name,
table_name, 
delete_rule
from dba_constraints 
where constraint_type = 'R' 
and delete_rule!='NO ACTION'
and owner not in ('SYS', 'SYSTEM','DBSNMP','EXFSYS','SYSMAN','CTXSYS', 'OLAPSYS');