{"id":43683,"date":"2020-02-12T17:09:23","date_gmt":"2020-02-13T00:09:23","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/?p=43683"},"modified":"2022-06-22T13:44:29","modified_gmt":"2022-06-22T20:44:29","slug":"kb00010399-cleanup-issue-for-finished-batches-in-2019-1","status":"publish","type":"post","link":"https:\/\/ephesoft.com\/docs\/kb00010399-cleanup-issue-for-finished-batches-in-2019-1\/","title":{"rendered":"Transact 2019.1 Cleanup Issue for FINISHED Batches"},"content":{"rendered":"
Environment<\/strong>:<\/p>\n Ephesoft Transact 2019.1 on Windows with MSSQL database.<\/p>\n Issue<\/strong>:<\/p>\n There is an issue in Ephesoft Transact 2019.1 where the FINISHED batches in the Batch Instance Management screen do not get cleaned up using the CLEANUP job. The following error appears in the dcma-report-all.log<\/strong><\/p>\ncom.ephesoft.dcma.report.service.EtlServiceImpl \u2013 ess-sync_hist_manual_steps_in_workflow \u2013 An error occurred, processing will be stopped:\r\n\r\nCouldn't execute SQL : MERGE hist_manual_steps_in_workflow AS TARGET\r\n\r\nThe MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more than one source row. A MERGE statement cannot UPDATE\/DELETE the same row of the target table multiple times. Refine the ON clause to ensure a target row matches at most one source row, or use the GROUP BY clause to group the source rows.<\/pre>\n