System Monitoring and Diagnostics Guide for Siebel eBusiness Applications > 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 need to 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 may 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 will periodically update 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 may 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 may 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 may then resume or stop the paused task.

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

  • 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 may take a while, in which case you may issue another Stop command, and the shutdown will be forced (this state may appear as Forcing Shutdown). After a task has been instructed to stop, it may not be resumed.
  • Completed. Indicates that the task is no longer running. After a task is completed, it may not be restarted, though you may 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 6).

Table 6.  Task Status Fields
GUI Column Name
Command-Line Interface Column Name



The state of the task using the appropriate language code.



Every component task sets various state values during the course of its operation. The Status column in the tasks view and the TK_STATUS column in the command-line interface displays the value for the state value Task Status (alias TaskStatus).

State (Icon)

Not applicable

A stoplight representation of the state of the task. Green indicates normal conditions. Yellow indicates temporary non-operational conditions. Red indicates a non-operational condition. Clicking the icon field reveals the state value associated with the color code.

About Siebel Server Task IDs

Siebel Server Task IDs identify Siebel Server tasks and are referenced in various views of the GUI as well as in both Siebel Server and component log files. These identification numbers can help you locate individual tasks and their applicable log files. See About Siebel Server Log Files for details on event logging and log files.

Task IDs are assigned sequentially from each Siebel Server for each Siebel Server task beginning at 1. Each time the Siebel Server is restarted, Task ID numbers are increased by 1000. The maximum task ID number that can be assigned is 262144 (256*1024). After the maximum task ID number is reached, the task ID number begins again at 1.

System Monitoring and Diagnostics Guide for Siebel eBusiness Applications