How to delete running jobs from the Core Console using table QRTZ_JOB_DETAILS.

11 de Dezembro de 2013 15:30

Question

In Client Automation Enterprise (CAE),it is not possible to delete running jobs using the Core Console or the Enterprise Manager. How can these jobs be deleted and removed from the Console's Current Jobs list?

Answer

If that does not work, In a Core & Satellite environment,these job executions can be deleted by doing the following:

Open a command prompt and navigate to <HPCA>\database\bin.
Run mysql.exe -u ope -p ope.
Type ope and press Enter.
Run a SQL command to delete the running job executions.

To delete the parent job, not an individual job execution,copy its ID and run:

delete from QRTZ_JOB_DETAILS where JOB_NAME=X; (Where X is the ID for the parent job and ";" is used to commit the command).

. This will delete the parent job and all job executions under it.

3 comentários

iniciar sessão para comentar.

Previous 3 comentários

Data Votos

Alex Taylor

26 de Janeiro de 2016 02:03

Thanks for this answer. It work for me on Version 9.0

Craig Tonner

26 de Janeiro de 2016 09:06

Personally I don't believe that anybody should be encouraged to fiddle with the MYSQL database.

If you cannot delete running jobs from the Core Console webpage then it should be raised as an issue and an enhancement should be introduce to fix this.

MySQL is so problematic I have no idea why it's their considering we all have enterprise SQL or Oracle servers in place and being used for inventory.

Ana Caldas

26 de Janeiro de 2016 14:39

Craig, thanks for bringing that up. I agree that this should only be used when absolutely necessary. I feel like this post was supposed to be a continuation or reply to this other article (which contains a warning). My suggestion is, if a job ever gets stuck for several days, and you're comfortable with MySQL and want to risk running the command by yourself, try deleting the problematic job execution first. Usually, the whole parent job is waiting on just one job execution. If the parent job still keeps showing up as "running" even though all job executions have ended or have been deleted, then it may be necessary to delete it from QRTZ_JOB_DETAILS.