You can translate the question and the replies:

Denodo Scheduler

Hi to everyone, I have two question about Denodo Scheduler. 1. The first one is: how can I kill a Scheduler process when the stop button doesn’t work? I tell you my case: I have created a VDP Job with a JDBC exporter and the extraction was in contrast with the primary key constraint and when this job has started I was not able to stop it (even with the stop button, I was forced to delete this job in order to continue to use the destination table). I know that is possibile to avoid this problem, but I’d like to know if it was possible to repair to this error. ![Problem with Denodo Scheduler](https://imgur.com/eCyEB1r) 2. The second question is how, with the Scheduler, can I update the destination table either without delete content or duplicate rows? I try to write an appropriate sql statement in the Extraction section’parameterized query space. but the job does not work because it would seem that only the table from the data sources can be used in the query ![not found](https://imgur.com/Vb5Lroi) Thank you in advance LDB
scai finance Denodo Scheduler 7.0
user
18-10-2019 06:16:26 -0400
code

3 Answers

Hi, 1. I would first check the <Denodo_Home>/logs/scheduler logs for any errors related to stop button functionality. I am not able to see your image but try to restart the Scheduler server and Scheduler administration tool, this will bring back the job to its original state. You can use [Query Monitor](https://community.denodo.com/docs/html/browse/7.0/vdp/administration/installation_and_execution/launching_the_virtual_dataport_administration_tool/query_monitor) to kill the query that was started by the VDP job from the Scheduler tool. 2. You have two options in the exporter section **Delete table content** and **Update tuple if entry already exists in DB** options that will help remove duplicates and maintain uniqueness. To know more on these features, you can refer to section **JDBC** in the [Exporters That Can Only Be Used In Non-VDPIndexer Jobs](https://community.denodo.com/docs/html/browse/7.0/scheduler/administration/creating_and_scheduling_jobs/configuring_new_jobs/postprocessing_section_exporters#exporters-that-can-only-be-used-in-non-vdpindexer-jobs) under the Postprocessing Section (Exporters) of the Scheduler Administration Guide. Hope this helps!
Denodo Team
21-10-2019 05:46:30 -0400
code
Thank you for the answer, but with the option **Delete table content** I am the only user that could update the destination table: any update made by anyone other will be lost.
user
22-10-2019 04:37:02 -0400
Hi, In this case, I would just use the **Update tuple if entry already exists in DB** option so I will not delete any content from the table. This option will make sure only the tuples that are being processed by you will be updated and the other records in the table will be untouched. Hope this helps!
Denodo Team
06-11-2019 06:58:06 -0500
code
You must sign in to add an answer. If you do not have an account, you can register here