Foreign key constraint violation
- Last UpdatedApr 24, 2025
- 1 minute read
This issue typically occurs when rows have been manually deleted from the table that the given table depends on. You will see an error message similar to the following:
06/24/97 01:47:08 - Failed to update EFM..gasQualityHistory:
Foreign key constraint violation occurred, dbname = 'EFM',
table name = 'gasQualityHistory', constraint name = 'fk1_gasqualityhistory'.
1 > insert into gasQualityHistory values (0, 867109003, 0,
'gasqual_e', 1020.000000, 0.620000, 0.020200, 0.011000, 0.005000, 0.010000,
0.001000, 0.000100, 0.950000, 0.002000, 0.003000, 0.000500, 0.004000,
0.000700, 0.000600, 0.000800, 0.000900, 0.000100, 0.000100, 0.000200,
0.000400, 0.000300, 1)
To solve this problem
DPdirect will automatically Datapump the foreign keys if the constraint violation is only one level deep. If it is more than one level, then you need to manually resynchronize the database using the DPutil program.