Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Experiencing the error: NULL result in a non-nullable column during replication even though source data doesn't have null values on the key columns.
In the transformation output, we are defining HASH_KEY: hash_sha256(ifnull($C1,'NULL')||ifnull($C2,'NULL'))
C1 and C2 are key columns (a composite primary key) from source.
In the target, we are only treating HASH_KEY as key column.
Has anyone experienced? If so, any help? I can provide further details if required. thank you!
Hello @SujiKittu08 ,
We need additional information to understand the issue. Please open a support ticket with:
1. The source table creation DDL include PK and Index information
2. In target endpoint, set keepCSVFiles & KeepErrorFiles to true
3. In target endpoint, reduce "Batch load timeout" and "Max file size" to generate smaller CSV files.
4. If the issue occurs in Full Load stage:Set source_unload/target_load to Verbose (all other set to default). If the issue occurs in Change Processing stage:Set source_capture/target_apply to Verbose
5. re-create the issue then
5.1 download the task Diag package
5.2 decrypt the newly generated task log files, compress them and attach the case
5.3 attach the newly generated CSV files in step (2)
Please share the support case number, We'd like to work with support team together on it.
Regards,
John.