FAILED TRYING TO EXECUTE ON CONNECTION glide.11 (connpid=2858872): INSERT INTO sys_progress_worker(

[Rowella Montell]

Hi,

Good Day!

We have created a Data Source with Robust Import Set Transformer for new CI creation in cmdb_ci table. This was deployed in Prod and was working fine for a few weeks until we encounter an error below. It seems like we are getting a duplicate sys_id in sys_progress_worker table. Can anyone advise as to what to check and possible actions we can take to resolve the issue? As per checking on the script we have created in the script include we have no script pertaining to the sys_progress_worker table.

We are currently only getting this error in Prod and not in lower instance.

Error:

FAILED TRYING TO EXECUTE ON CONNECTION glide.11 (connpid=2858872): INSERT INTO sys_progress_worker (`sys_id`,`sys_updated_by`,`sys_created_on`,`sys_mod_count`,`run_in_background`,`sys_updated_on`,`state`,`message`,`sys_created_by`) VALUES('3f07f4fedb1fc550cb566f5405961936','user_adm','2022-05-10 02:11:00',0,'false','2022-05-10 02:11:00','unknown','Starting','user_adm') /* pdi036, gs:glide.scheduler.worker.6, tx:c8173cfedb1fc550cb566f5405961967 */
Unique Key violation detected by database ((conn=2858872) Duplicate entry '3f07f4fedb1fc550cb566f5405961936' for key 'PRIMARY')
: java.sql.SQLIntegrityConstraintViolationException: (conn=2858872) Duplicate entry '3f07f4fedb1fc550cb566f5405961936' for key 'PRIMARY':

[Anil Lande]

Hi,

I guess you are trying to get answer for your question since last 15-20 days. If you do not get expected response and if your issue if happening on Prod then you can prefer to get support from ServiceNow support team.

Please raise a case with ServiceNow for the same on http://support.servicenow.com/. Please connect with your team internally and raise a case to get support.

Thanks,
Anil Lande

[Wei_ Ling]

Did you solve the problem? I had the same problem

[Rowella Montell]

Hi Wei_ling,

We have resolved the issue. We have ETLs set up with these datasources and we have getting the errors on there as well when we run it again manually on the dev instance. Upon checking the 'class' field was added and mapped in the attribute field mapping for some of the classes thus returning that error. We just removed that field and it worked fine.

[ersureshbe]

Hi,

Can you check both records and identify the source and remove one try to run the job. If it updates, just check how other record is created?