Help Center/
ROMA Connect/
Troubleshooting/
Composite Data Integration Tasks/
Inserted Data Violates the Non-null Constraint
Updated on 2022-02-21 GMT+08:00
Inserted Data Violates the Non-null Constraint
Cause Analysis
The task fails to be executed. The following information is displayed in the log:
Solution
Perform the following operations to resolve the issue:
- This field in the source table is set to null, but is set to a non-null value in the destination table. To resolve this issue, modify the field attributes in the source and destination tables to ensure consistency.
- A redundant table mapping is configured during task creation. Therefore, data in the source table with a similar name is collected to the destination table. As a result, empty data is written to the field. To resolve this issue, correctly configure the table mapping.
- In the redo logs generated by the Oracle database, the WHERE condition is missing in the field of the UPDATE statement. As a result, the value of this field is missing. To resolve this issue, add the WHERE condition to the field of the UPDATE statement.
Parent topic: Composite Data Integration Tasks
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot