Siebel System Monitoring and Diagnostics Guide > Monitoring Siebel Server Run-Time Operations >

About Siebel Server Task States

A Siebel Server task is an instantiation of a Siebel Server component. To run a Siebel Server task, you must run a component job, which requests one or more Siebel Server tasks to run. For information on component jobs, see Siebel System Administration Guide.

A Siebel Server task might be in one of four fundamental states: Running, Paused, Stopping, or Completed.

• Running. Indicates that the task is executing normally. While the task is running, it periodically updates its task status, a component-generated message that indicates the task progress (or phase of operation).
  • Background mode component tasks run until stopped manually, or until the Siebel Server or the server component shuts down.
  • Batch mode component tasks run to completion when their assigned unit of work is done.
  • Interactive mode component tasks run until the client signs off from the connection (or until the task, server component, or Siebel Server is shut down).

    You might explicitly stop any currently running component task.

• Paused. Indicates that the task has been temporarily placed in a suspended state. A paused task does not exclusively hold any shared system resources (such as file locks or database locks), or expend any processor or I/O cycles. You might choose to pause a running task to temporarily free up the system to process other critical tasks without having to restart the entire task. You might then resume or stop the paused task.

  NOTE:  Only tasks from certain component types can be paused. For a list of these component types, see Siebel System Administration Guide.

• Stopping. Indicates that the task has been instructed to stop, or the server component or Siebel Server is being shut down. Occasionally, the shutdown process might take a while, in which case you might issue another Stop command, and the shutdown is forced (this state might appear as Forcing Shutdown). After a task has been instructed to stop, it might not be resumed.
• Completed. Indicates that the task is no longer running. After a task is completed, it might not be restarted, though you might start a new task for the same server component. Several variations exist for the Completed state, depending on the manner in which the task finished processing:
  • Completed indicates that the task ran to completion and exited normally (batch mode and interactive mode tasks only).
  • Exited with Error indicates that the task encountered an error during its processing (such as bad input values or database errors). In this case, the Task Status field displays the error identifier for the error that has occurred.
  • Killed indicates that the task was not able to shut down cleanly, and you forced the task to shut down.

About Task Status Fields

Each Siebel Server record has three fields in which the Siebel Server status appears. Table 15 provides the task status fields.