ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Autosys Scheduler Non-existent jobs in Table


Article ID: 145688


Updated On:


CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent CA Workload Automation AE



How to clean up non-existent jobs in ujo_ext_job table?  Quite a few of these. 

EXT_AUTOSE,EXT_JOB_NAME                                                    ,    STATUS


DC3       ,1GSF_FDS_OTIBRINTRADAYFEED_SOD_BOX_QA                           ,         1

DC3       ,1GSF_FDS_OTIBRINTRADAYFEED_TRANSFORM_BOX_QA                     ,         1

DC3       ,1GSF_FDS_PRICE_LOAD_BOX_QA                                      ,         1

DC3       ,1GSF_REPO_DM_ART_TO_GSF_BOX_QA                                  ,         1

DC3       ,1GSF_REPO_DM_ART_TO_GSF_META_FW_QA                              ,         6

DC3       ,1GSF_REPO_DM_ART_TO_GSF_NONMETA_FW_QA                           ,         6

DC3       ,1IDB_DRSBATCH_OperationsReporting_Box                           ,         0

DC3       ,                               ,         0


Release : 11.3.*

Component : CA Workload Automation AE (AutoSys)


Please consult with the DC3 instance to determine whether the jobs are defined there.
When you define a job and specify a job condition with dependency on a job in a remote instance, the application server on the local instance sends a registration event to the remote instance for the scheduler to process. As the remote scheduler sends job status updates to the local instance, the local scheduler keeps track of the status by creating a row in ujo_ext_job. When you update the job to remove the dependency on the job from the remote instance, the application server is supposed to send notice to the remote scheduler. At the same time, the scheduler is supposed to remove the job entry from ujo_ext_job automatically.
If you are sure that no local jobs reference the remote jobs in their job condition attribute AND you are sure that the jobs no longer exist in the remote instance, then you can delete the rows without harm to the scheduler.