multiple events that are stuck
Article ID: 213442
Updated On:
Products
Autosys Workload Automation
Issue/Introduction
We have a box job that is stuck. Our user kept trying to force start or change the status on the box without checking the status on detailed report.
How can we best clear all those stuck events?
The following is the sample data from Detailed Report
Job Name Last Start Last End ST/Ex Run/Ntry Pri/Xit
________________________________________________________________ ____________________ ____________________ _____ ________ _______
abcjobnametest1 04/21/2021 22:55:56 ----- RU 99141444/2
Status/[Event] Time Ntry ES ProcessTime Machine
-------------- --------------------- -- -- --------------------- ----------------------------------------
[FORCE_STARTJOB] 04/21/2021 08:23:20 0 PD 04/21/2021 22:55:56
RUNNING 04/21/2021 08:23:20 1 PD 04/21/2021 22:55:56
[FORCE_STARTJOB] 04/21/2021 22:02:51 0 PD 04/21/2021 22:55:56
[FORCE_STARTJOB] 04/21/2021 22:03:56 0 PD 04/21/2021 22:55:56
[FORCE_STARTJOB] 04/21/2021 22:04:33 0 PD 04/21/2021 22:55:56
[KILLJOB] 04/21/2021 22:08:21 0 PD 04/21/2021 22:55:56
SUCCESS 04/21/2021 22:20:12 0 PD 04/21/2021 22:55:56
RUNNING 04/21/2021 22:55:56 2 PD 04/22/2021 00:01:03
RUNNING 04/21/2021 22:55:56 2 PD 04/22/2021 00:01:05
RUNNING 04/21/2021 22:55:56 2
TERMINATED 04/21/2021 22:55:56 1
SUCCESS 04/21/2021 22:56:28 2
[KILLJOB] 04/21/2021 22:58:33 0
[KILLJOB] 04/21/2021 22:59:21 0
SUCCESS 04/21/2021 23:00:16 0
[KILLJOB] 04/21/2021 23:03:06 0
[KILLJOB] 04/21/2021 23:04:20 0
[KILLJOB] 04/21/2021 23:06:27 0
FAILURE 04/21/2021 23:07:00 0
[KILLJOB] 04/21/2021 23:21:04 0
[JOB_ON_ICE] 04/21/2021 23:22:34 0
TERMINATED 04/21/2021 23:23:07 0
INACTIVE 04/21/2021 23:52:04 0
SUCCESS 04/22/2021 00:02:08 2
[KILLJOB] 04/22/2021 01:48:40 0
[KILLJOB] 04/22/2021 01:50:48 0
TERMINATED 04/22/2021 01:54:37 0
Environment
Release : 11.3.6
Component : AutoSys
Resolution
The events for the job stream were not getting processed even though their time had come.
There was a lock in the database preventing the jobs from being accessed.
Restarting the scheduler released the lock and then allowed the unprocessed events to be processed.
Feedback
Yes
No
Powered by
