ABOR-DB ERROR | Description:The task aborted, then in a condition, an error occurred causing a DB ERROR status change. Since the task already completed, the status was set to the first few letters of that completion status (i.e. ABOR) plus a hyphen and DB ERROR. Action:SeeDB ERRORstatus. |
ABORTD | Description: The task has terminated in an unsuccessful manner on the agent. This is an interim status that will change almost immediately to ABORTED. Action:Wait for the status to change to ABORTED. |
ABORTED | Description:Applications Manager has processed the task and it terminated unsuccessfully. Action:To see why the task aborted, check the system output file and view/edit the task details in the Backlog. |
AGENT WAIT | Description:The task is assigned to an agent that does not have enough threads or CPU available to process the task. Action:The task will be processed as soon as there are available threads/CPU capacity. If this status occurs often, you may want to change the thread schedule assigned to the agent. |
BAD BATCH | Description:There is no defined application information for BATCH registered in Applications Manager. Action: Define a BATCH application. |
BAD CONDITN | Description:A SQL statement or check file BEFORE or AFTER condition has returned an error in the task. Action: Edit the conditions and/or their SQL statements for the task in the Backlog and in the job/process flow definition. Make sure you have sufficient tablespace where applicable. |
BAD CONNECT | Description:The host login and password combination that is specified for the task is in error. Action: Check the login and password assigned to the job or process flow component. |
BAD DATE PRM | Description:The date format required by the argument type is incompatible with the prompt. Action:Check the dates entered for a prompt if one exists, or check the dates passed to a prompt or condition by a substitution variable. |
BAD LIBR | Description:The library associated with this job includes a path that cannot be found. Action:Edit the library's path. |
BAD LOGIN | Description:The login specified for the task is invalid. Action: There may be a database problem. Check with your DBA to make sure the correct Database ID is specified in the job definition. |
BAD MJN | Description:The task's job sequence number is incorrect and does not match the currently registered job known to Applications Manager. Action: Have your DBA check the Applications Manager database to see if there is a bad entry in theso_job_tabletable. |
BAD MODULE | Description: A bad job name was entered for a REQUEST JOB action in a condition. Action:Edit the condition that generated the entry in the Backlog. |
BAD QUEUE | Description:A condition with the CHANGE QUEUE action has been met. The designated alternate queue, however, does not exist in Applications Manager. Action:Edit the condition that generated the entry in the Backlog. |
BAD SQL STMT | Description:A SQL statement associated with a dynamic substitution variable used by this task is incorrect. Action: Dynamic substitution variables can be used in prompts and conditions. Check what substitution variables are used in the prompts and conditions for this job or process flow. |
BAD TYPE | Description: The data type specified for the task is incorrect. Action:Check the data type definition assigned to the prompt. |
BAD_AGENT | Description: The agent assigned to the job does not exist. This status will only occur if the agent was defined through a direct entry into the Applications Manager database. Action:Select an agent for the job. |
CANCELLED | Description: A condition on this task, or on a previous component in the process flow, has cancelled the remaining process flow components. Action:Check the conditions specified in the components of this process flow. |
CONDITN WAIT | Description: The task is waiting for a condition to be met before executing. Action: No action is required. You can check the conditions for this task in the Backlog. |
DATE PENDING | Description:This task is not yet ready to run. Tasks are not ready to run if: - They have been staged by running either the STAGING or STAGING_BY_SCHEDULE jobs and selecting prompts.
- Someone post-dated the start date/time for a job or process flow when requesting it.
- A condition with a DELAY TASK action prohibits the task from running.
Action: No action is required. The task will run when its reaches its start date and time, or when its conditions allow it to. You can edit the task details of the job or process flow in the Backlog. |
DB ERROR | Description:An internal database error has occurred while processing this task. Possible causes include: - Subvars in prompts or conditions that use SQL have returned an error when run from the command line, such as SQL with a bad database link.
- The inability of the Applications Manager processes were unable to connect to the automation engine's database (network problems).
- A database or database server crashed.
Action: Try resetting the task—if that works, then the error was resolved prior to the reset. Useful troubleshooting information can be found in the following locations: - The system output file (viewable from theOutput Filestab of theTask Detailswindow).
- The comments (viewable from theCommentstab of theTask Detailswindow).
- TheAgentServiceandRmiServerprocess logs in thelogdirectory.
|
DEAD | Description:The process associated with this task can no longer be found on the host system. This is an interim status that will change almost immediately to DIED. Action:Wait for the status to change to DIED. |
DELETED | Description:The task has been deleted from the Backlog. Action:Find out why the operator deleted the task and resubmit the task if necessary. |
DIED | Description:The process associated with this task can no longer be found on the host system. This happens if a process takes more than five minutes to begin execution after initiation. Usually there is a problem with the agent that prevents the task from executing. If the task's status is still RUNNING at the time that the process disappears from the host system, the task may have been killed from the operating system. Action:Check to see if the agent is running. Check to see if the task was killed from the operating system. |
ERRORS | Description: If you see this status in the Backlog, Applications Manager detected an error in a condition. You may also see listings for the RMI server or your agents in History with an ERRORS status. These are informational only. For more information, see the status of your automation engine and agents. Action: To see why the task with a bad condition went into this status, check the system output file and view/edit the task details in the Backlog. |
FILE ERROR | Description:Thetmpfile could not be created. Action:Check that the disk is not full or for improper file and directory permissions. |
FIN-DB ERROR | Description:The task finished, then in a condition, an error occurred causing a DB ERROR status change. Since the task already completed, the status was set to the first few letters of that completion status (i.e. FIN) plus a hyphen and DB ERROR. Action:SeeDB ERRORstatus. |
FINISHED | Description: The task has successfully completed its operation. Action:No action required. |
HOLD | Description:The task has had its execution delayed indefinitely because: - The task has a condition with a HOLD TASK action.
- TheHold Taskbox was checked for a job/process flow that was requested on an ad hoc basis.
- The task in the Backlog has been put on hold.
Action:The task will remain on hold until the status is changed by an action associated with another condition or by a user. |
HOLD PRED WT | Description: The task is on holdandis waiting for one or more predecessor requirements to be met. Action:The task will not be eligible to run until both of the following occur: - The hold status is changed by an action associated with another condition or by a user.
- The predecessor requirements for the task are met.
|
HOST FAILURE | Description:An error occurred when the host attempted to execute the command required to perform the task. This usually indicates a lack of process slots on the system or an inadequate sub process limit for the Applications Manager account. Action:Check with your Applications Manager administrator. |
INACTIVE | Description:This task was skipped because theActiveoption in its job, process flow, or agent definition is unchecked. Action:No action required. |
INITIATED | Description:One or more of the components in this process flow have been initiated and all the components in the process flow have not yet finished. Action:No action required. |
KILL | Description:A request to terminate the task while it was executing on the host was issued by a user or by an action associated with a condition. This is an interim status that changes almost immediately to KILLED. Action:See the explanation for the KILLED status. |
KILL1 | Description:Used by the OAE extension when the automation engine is evaluating a task that is being killed. When the agent successfully kills the task, it sets the task's status to KILL. The automation engine evaluates any post-processing conditions and sets its status to KILLED. Action:See the explanation for the KILLED status. If you wish, you can resubmit the task. |
KILLED | Description:Applications Manager has processed the task after a request for termination has been made for it. The task has therefore been removed from the host system. Action:If the task is still in the Backlog, you can reset it. |
KILLING | Description: Used by the OAE extension when the automation engine has sent the command to the agent. When the agent successfully kills the task, it sets the status to KILL. The automation engine evaluates any post-processing conditions and sets the status to KILLED. Action:See the explanation for the KILLED status. If you wish, you can resubmit the task. |
LAUNCH ERR LAUNCH ERROR | Description: The automation engine had an error launching the task. Possible causes include: - Oracle errors when launching the task
- Machine disk space issues
- Machine performance issues, or network issues (such as a hung port, network slowness, or firewall changes)
With regard to network issues, LAUNCH ERR can mean that the task start command didn't reach the agent
(automation engine-->|agent), or it can mean that the agent didn't respond back (automation engine|<--agent). Action:Before calling Automic support, check the following for errors: - Task's comments (in the Backlog or History, right-click the task and go toComments)
- Unregistered task log files on the machine. (Check in theoutdirectory on the machine where the task was supposed to run. It may have started running, but couldn't register the output.)
- TheRmiServer.<time stamp>.logfile in the automation engine'slogdirectory. This file may include errors starting withAwE.
- The latestAgentServicelog files for the local or remote agent. These may include errors starting withERR.
If you find errors, search for them in the Knowledge Base on the Automic Support Web site or call Support. Before contacting Support, have the log files listed above ready to send. |
LAUNCHED | Description: The task has been launched, but its status has not yet been determined. Action:No action required. |
MAX RESTARTS | Description:The task has been restarted 99 times. This is the maximum number of times a task can be restarted. Action:To run the task, delete and resubmit. |
MGRSTOPPED | Description:This status is displayed only in History. It is associated with the agents. It indicates the date and time theAgentServiceprocess stopped. Action:No action required. This is only a historical record. |
Min Run Time | Description:The task finished more quickly than the time specified in theMin run timefield of the job's definition. Applications Manager developers specify a min run time when they expect a job to run for at least the time they specify. Action:Investigate why the task finished so quickly. |
NO PRIORITY | Description:This task has been scheduled with a priority of zero. Since no priority has been assigned to the task, it cannot be executed until a priority is set. Action:Change the priority for the task in the Backlog and/or edit the job/process flow definition. |
PRED WAIT | Description: The task is waiting for a predecessor requirement to be met before executing. Action:No action required. Predecessors can be edited for the running of a task in the Backlog if the task is in a non-running status. |
PW-DELETE | Description: The component in a process flow was waiting for a predecessor requirement to be met before executing and it has been deleted. The component remains in the Backlog as a placeholder for predecessor inheritance. Action:No action required. |
PW-SKIP | Description: The task was waiting for a predecessor requirement to be met before executing and it has been skipped. Action:No action required. |
QUEUE WAIT | Description:The job is assigned to a queue that does not have enough threads available to process the task. Action:The task will be processed as soon as there is an available thread. If this task should be running, make sure that: - The queue has not been inactivated.
- The thread schedule assigned to the queue has an adequate number of threads in itsMax run timesetting to allow the appropriate number of concurrently running tasks.
Queue definitions can be altered from theExplorerwindow or from theQueueswindow. You can change the queue for the particular running of a task in the Backlog on theTask Detailswindow. |
QUEUED | Description: The task has been sent to an Applications Manager queue, but has not been processed by the automation engine to determine execution eligibility. The status should quickly be updated. The execution order of tasks waiting to run in a QUEUED status is decided in the following order: - Queue priority
- Job priority
- Start date and time
Therefore, if two tasks are waiting to run in different queues, and those queues have the same priority, the jobs' priorities are checked. If queue and job priorities are the same, their start dates and times are compared. Action:No action required. |
RECURSIVE | Description:The components within this process flow are recursive, calling one another in an infinite loop. This only happens in process flows that were created in a previous Applications Manager version. Action:Edit the process flow to change its components' predecessor requirements. |
RESV THRDS | Description:The job's queue has reserved threads but none are available. Action:The task will be processed as soon as there is available threads. |
SELF WAIT | Description: TheSingle runoption is set for the job or process flow, and there is another instance of the task running. The first must complete before the second instance will be initiated. Action:No action required. If you want to allow two instances of the task to run concurrently (even within a process flow), uncheck theSingle runoption in the job/process flow definition. |
Skip!Active | Description:This process flow component was skipped because ioption is unchecked. Action:No action required. |
Skip!DayofWk | Description:This process flow component was skipped because the corresponding day of the week was not assigned to it. Action:No action required. |
Skip!RunCal | Description:This process flow component was skipped because a run calendar assigned to it did not include this day. Action:No action required. |
SkipCal | Description:This process flow component was skipped because a skip calendar including this day was assigned to it. Action:No action required. |
SkipCond | Description:The task will not be run because an action associated with a condition has specified that the task be skipped. Action:Check the conditions for the job/process flow. |
STAGED | Description:This process flow component is part of a process flow that has been staged. Tasks are staged by: - Running either the STAGING or STAGING_BY_SCHEDULE jobs and selecting prompts.
- Post-dating the start date/time for a job or process flow when requesting it on an ad hoc basis.
The components will stay in a staged status until their process flow is initiated. Staged and post-dated jobs and process flows in the Backlog will be shown in a DATE PENDING status. Action:No action is required. The task will run when its reaches its start date and time. You can edit the task details of the process flow or its components in the Backlog. |
STAGED HOLD | Description:This process flow component is on holdandhas been staged. Action:The task will not be eligible to run until both of the following occur: - The hold status is changed by an action associated with another condition or by a user.
- The task reaches its start date and time.
|
STAGED_PW | Description: This process flow component has been stagedandis waiting for one or more predecessor requirements to be met. Action:The task will not be eligible to run until both of the following occur: - The task reaches its start date and time.
- The predecessor requirements for the task are met.
|
STARTED | Description: This status is displayed only in History. It is associated with the RMI server or an agent. It indicates the date and time the RMI server or agent started. Action:No action required. This is only a historical record. |
STG SKIP | Description:This process flow component has been stagedandis being skipped in the process flow. This happens when a day of the week is unchecked or a skip calendar is selected in theSchedulebox on the component'sGeneralsub-tab. When its process flow runs, this task will move to History with a Skip!Active status. Action:No action required. |
STG_PW HOLD | Description:This process flow component is on holdandhas been stagedandis waiting for one or more predecessor requirements to be met. Action:The task will not be eligible to run until all of the following occur: - The hold status is changed by an action associated with another condition or by a user.
- The task reaches its start date and time.
- The predecessor requirements for the task are met.
|
STOPPED | Description: This status is displayed only in History. It is associated with the RMI server or an agent. It indicates the date and time the RMI server or agent stopped. Action:No action required. This is only a historical record. |
TIMEDOUT | Description:The automation engine has processed the task after it has exceeded its permitted run-time allotment. Action:Determine why the task was taking so long to run. If appropriate, change the maximum run time for the job, or change the task's conditions. |
TIME-OUT | Description:The task has taken longer than the maximum run-time period specified in the job definition or a maximum run-time period specified in a condition. This is an interim status that should change quickly to TIMEDOUT. Action:See TIMEDOUT for actions. |
UNAVAILABLE | Description:The required agent is not running. Action:Start the agent. |
UNKNOWN | Description:The agent cannot update the automation engine for unusual reasons. Action:Check the agent log file for errors. |
UNSAT-FINISH | Description:Someone has removed this task as a predecessor to all referenced tasks. The predecessor links of other tasks need to be satisfied by another running of this task. For more information, seeUnsatisfying Tasks as External Predecessors in History. Action:No action required. |
WARNING | Description:An Applications Manager run-time extension changed the status of a job to WARNING. Usually this status is assigned to a task that has errors but has gone to completion. Action:Check the log for the task to see what errors occurred. |