Jobs ends in Launch Error with "not in job queue" output error

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

A Launch Error is set by the RMI process anytime an Agent does move a Task from Launched status to Running status within 5 minutes. 

This may occur for many reasons and the behavior surrounding the Launch Error gives a clue into why it might occur. 

One of the behaviors seen is that the output file is generated after the RMI has set the Task to Launch Error status. Taking a look at the output file, the following errors are seen:

ERROR -999 ORA-20094: Jobid 27544136.00 not in job queue
ORA-06512: at "APPWORX.AW4", line 341
ORA-06512: at line 1
ORA-06512: at "APPWORX.AWDYN", line 23
ORA-06512: at line 1

Environment

Release : 9.3

Component : APPLICATIONS MANAGER

Cause

The "out" directory may have millions of files causing performance delay when reading and writing to the directory.

This may occur if the output retention value for Jobs is set too high (default 7 days).

Resolution

Check the $AW_HOME/out or %AW_HOME%\out directory to make sure the directory does not have millions of records.

If millions of records are found, clean up on this directory is required to resolve the issue