The duplicate key value violates unique constraint error usually occurs when two jobs are submitted under the same job ID. When the first job completes, this is recorded in the fme_job_history table in the System Database, then when the second job completes it also tries to add a record to this table, but cannot because the ID already exists, hence a duplicate key value error.
To resolve this error, you could first try and delete the record from the fme_job_history table. This should allow the second record to be entered and things should continue running as normal.
The duplicate key value violates unique constraint error usually occurs when two jobs are submitted under the same job ID. When the first job completes, this is recorded in the fme_job_history table in the System Database, then when the second job completes it also tries to add a record to this table, but cannot because the ID already exists, hence a duplicate key value error.
To resolve this error, you could first try and delete the record from the fme_job_history table. This should allow the second record to be entered and things should continue running as normal.
In the end we removed the specific job (id = 37020) from the database table 'fme_jobs'.
A delete of the specific row was not possible (probably the same query when request from the FME Server interface). There was only one job (the job with id = 37020) so we did a truncate on the table.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
