Oracle integrity constraints are incorrect. oracle integrity constraints

Oracle integrity constraints are incorrect. oracle integrity constraints

Error
Caused by: org. hibernate. exception. ConstraintViolationException: cocould not execute JDBC batch update
ORA-02291: violation of complete constraints (UNISPOWER. FK932556A9840256A3)-parent keyword not found
Possible causes
A field in Table A is A foreign key associated with A field in Table B. This situation occurs when data is inserted into Table.

Possible causes:
1. When inserting data into Table A, the field associated with the foreign key must have data in Table B. This is the case if Table B does not have data.
2. A foreign key ring is generated, that is, the field associated with the foreign key in Table B is associated with the field in table C, but the corresponding field in Table C does not have data.
3. If it is not the above two cases, it is A very easy to neglect problem: the data type and length of the foreign key field in A and the field associated with the foreign key in B are inconsistent. In particular, the data length must be consistent.
The length of the Data Type in the master table and slave table is different.