Explanation:
There are three possible causes:
1. An <insert statement> or <update statement> issued on a table that is the referencing table in a <referential constraint definition> produces a row that is not a matching row of the <referential constraint definition>.
2. When deleting rows from a <referenced table> of a <referential constraint definition> with <action> RESTRICT in the <delete rule>, a matching row exists.
3. When executing a <referential constraint definition>, the <referenced table> or referencing table contains rows which conflict with the <referential constraint definition> to be created.
User Action:
1. Display the <referential constraint definition> using a <query statement> issued on the system table DOMAIN.COL_REFS_COL. Correct the <insert statement> or <update statement> according to this definition.
2. Use an appropriate <query statement> to determine which row of the referencing table prevents the desired <referenced table> rows from being deleted.
3. Use an appropriate <query statement> to determine which row of the <referenced table> or referencing table conflicts with the <referential constraint definition> to be created. Modify or delete the row concerned, or correct the <referential constraint definition> to be created.