Over the life-cycle of a job or step, the job execution status can change several times. The complete list of job statuses follows:
Scheduled: The job or step is scheduled to run at a designated time in the future.
Running: The job or step has started executing but has not yet finished. A job is defined to be in this state if at least one of its steps is currently running.
Initialization Error: The job or step could not be run for some reason (for example, the execution of a remote command failed because of an Oracle Management Agent internal error, incorrect credentials were specified, or the job includes an invalid path to a script). If a step in a job fails initialization, the job status is Initialization Error.
Failed: The job or step executed but did not accomplish its task.
Succeeded: The job or step executed completely.
Stopped: The job or step was canceled by the user.
Stop Pending: The user has stopped the job and currently running steps are completing execution. Once the running steps finish, the job status becomes Stopped if additional steps are present; if no additional steps, the status becomes Succeeded, Failed, or Failed Initialization.
Suspended: Special status indicating that the job execution is on hold. A job can be suspended for a number of reasons, leading to the following subcategories of the suspended state:
Suspend Pending: The user has suspended the job and currently running steps are completing execution. Once the running steps are complete, the job status becomes Suspended by User.
Suspended by User: The job was manually suspended by the user. A job can be created with an instruction for a step to suspend itself, which suspends the job.
Suspended on Lock: The job is blocked from running because it is waiting on a lock held by another process. It will automatically resume once the lock becomes available.
Suspended on Agent Unreachable: A job will be suspended if the job type is declared to be "agentBound," which means that the job will not execute if the Management Agent is down or unreachable due to network problems between the Oracle Management Service and the Management Agent. Check the network connection between the Management Service and the Agent. If the Agent is down, restart it. Typically, when the job is in this state, the job system retries the steps that could not be run before. Once the underlying problem is resolved, the job automatically resumes execution.
Suspended on Blackout: A job will be suspended if the job has been scheduled during a blackout window defined on any one of its targets with the "Run jobs" option off. (When creating a blackout, users can choose to run jobs or not). Jobs in this state will go to "Scheduled" after the blackout period ends and will eventually execute. Refer to About Blackouts for more information.
Inactive: A job target or the job owner was deleted. If a job owner is deleted, their jobs will be in an inactive state. Jobs are deleted in the background after their administrators are deleted.
Reassigned: The owner of the job has been removed from Enterprise Manager. Job ownership has been transferred to a new Enterprise Manager administrator.
Single vs. Multiple Execution Runs
Enterprise Manager Information Roadmap
Copyright © 1996, 2007, Oracle. All rights reserved.