Monitoring Siebel Server Run-Time Operations

Monitoring Oracle’s Siebel Server run-time operations is a necessary, on-going aspect of administering a Siebel application. Use metrics such as log files, state values, and statistics to monitor the Siebel application performance.

This chapter includes the following topics:

About Siebel Server States

After installation, a Siebel Server is always in one of the following states when connected to the Server Manager component (alias ServerMgr):

Starting Up. Indicates that the Siebel Server is in the process of starting up. When this process is complete, the state changes to Running.
Running. Indicates that the Siebel Server is running and that Siebel Server components can operate. This is the normal mode of operation for the Siebel Server. When the Siebel Server Service starts, it sets the Siebel Server to the Running state by default (depending on the value of the Auto Startup Mode Siebel Server-level parameter, which defaults to TRUE).
When the Siebel Server starts, its components are enabled and the default number of tasks is instantiated for the background mode components (the number of tasks is determined by the value of the Default Tasks parameter for each component).
Shutting Down. Indicates that the Siebel Server is in the process of shutting down. When this process is complete, the state changes to Shutdown.
Shutdown. Indicates that the Siebel Server is running, but component tasks are not currently running (other than the Siebel Server Manager component, which is operational whenever the Server Manager is connected) and new tasks are not allowed to start. The only processes that can run when the Siebel Server is in a Shutdown state are the Siebel Server System Service itself and the Server Manager for a Siebel Server Manager client.
Shut down the Siebel Server using the Server Manager whenever you want to shut down the:
- Server computer on which the Siebel Server is running. This allows a clean shutdown of each Siebel Server component.
- Siebel Server to perform maintenance.
- Siebel Server to perform an automatic upgrade on the Siebel Server’s software using Siebel Upgrade Wizard.
  
  Note: Individual components might be shut down or disabled without having to shut down the entire Siebel Server.

If the Siebel Server is not connected to the Server Manager component (alias ServerMgr), then the following states are applicable:

Not Online. The server component is not online. After the Siebel Server is restarted, this component state might occur temporarily before the component’s state becomes Online. If the status Not Online persists, then an error is preventing the component from becoming online. Check the component log and fix the error to let the component state become Online again.
Partially Offline. The server component is partially offline and cannot start until the Siebel Server is restarted.
- For a multithreaded component, if the number of active running processes is less than the value of the parameter MinMTServers, then the state is Partially Offline.
- For a background mode component, if the number of active running processes is less than the value of the parameter DfltTasks, then the state is Partially Offline.
Not available. Indicates that the Siebel Server has not been started. Indicates that the Server Manager cannot connect to the Siebel Server; you cannot run any tasks or perform any administrative functions on that Siebel Server.
Connect Failed. Indicates that Server Manager is able to get the connect string for the ServerMgr component from the Siebel Gateway but is unable to connect to the Siebel Server.
Handshake Failed. On startup, Server Manager sends a handshake request to the Siebel Server for the ServerMgr component. If that request fails, then this state occurs. Also, if the ServerMgr component on that particular Siebel Server cannot start any more tasks (because it has reached Maximum Tasks (alias MaxTasks) number of tasks) for the administration clients, then this state occurs. For more information about the MaxTasks parameter, see Siebel System Administration Guide and Siebel Performance Tuning Guide.
Login Failed. Server Manager connects to every Siebel Server for authentication. If the authentication fails for any Siebel Server, then the Login Failed state appears.
Disconnected. When Server Manager connects to the Siebel Server, the Siebel Server starts a task for the ServerMgr component. If that task exits (because of a malfunction or other problems), then the Disconnected state appears.

Siebel Server Status Fields

Each Siebel Server record has three fields in which the Siebel Server status appears. The following table provides the Siebel Server status fields.

GUI Column Name	Command-Line Interface Column Name	Description
Server State (Internal)	SBLSRVR_STATE	The state of the Siebel Server.
State	SV_DISP_STATE	The state of the Siebel Server using the appropriate language code.
State (Icon)	Not applicable	A stoplight icon representing the state of the Siebel Server. Clicking the icon in the State field reveals the actual state value associated with the stoplight color, which can be one of the following for example: Running (Green stoplight), which indicates normal conditions. Completed (Green stoplight), which indicates normal conditions. Exited (Red stoplight), which indicates a non-operational condition. Note: The State (Icon) field is blank when you are not connected to a Siebel Server.

About Siebel Server Component Group States

A component group might be in one of several states. The run state is dependent on the enable state; only component groups that have an Online enable state when the Siebel Server was started can have a run state of Online or Running:

Online. Every component within the component group is enabled to run tasks.
Running. Every component within the component group is enabled, and at least one component within the component group is running a task.
Shutdown. Every component within the component group is shut down. Tasks cannot run for any components within the component group.
Part shutdown. At least one component within the component group is shut down or shutting down.
Offline. Every component within the component group is offline.
Part offline. At least one component within the component group is offline or unavailable.
Starting up. At least one component within the component group is starting up.

Server Component Group Status Fields

Each Siebel Server component group record has three fields in which the status appears as shown in the following table.

GUI Column Name	Command-Line Interface Column Name	Description
State	CA_RUN_STATE	The state of the server component group using ENU language code.
Run State (internal)	CA_RUN_STATE	The state of the server component group using the appropriate language code.
State (Icon)	Not applicable	A stoplight icon representing the state of the Siebel Server component group. Clicking the icon in the State field reveals the actual state value associated with the stoplight color, which can be one of the following, for example: Running or Online (Green stoplight), which indicates normal conditions. Part Offline (Yellow stoplight), which indicates a temporary non-operational condition. Shutdown or Offline (Red stoplight), which indicates a non-operational condition.

About Siebel Server Component States

A Siebel Server component might be in one of the following states: Starting Up, Online, Running, Offline, Shutting Down, Shutdown, or Unavailable.

The Siebel Server component state is dependent on the assignment state of the component group to which it belongs; only Siebel Server components within assigned component groups when the Siebel Server was started can be Running or Online:

Starting Up. Indicates that the Siebel Server component is in the process of starting up. When this process is complete, the state changes to Online. When a new task is started for the component, the component state changes to Starting Up during the initialization phase and then to Running.
Online. Indicates that tasks are currently not running for the Siebel Server component, but new tasks might be started through the Siebel Server Manager (or in response to client requests, for interactive-mode components). When the Siebel Server starts, components for which processes are not started by default are online.
Running. Indicates that tasks are currently running for the Siebel Server component on the Siebel Server, and new tasks are allowed to start (up to the value of the Maximum Tasks parameter for the component). When the Siebel Server starts up, background-mode components for which processes are started by default (components with a Default Tasks parameter set to a nonzero value) start.
Offline. Indicates that new tasks might not be started for the component, though current running tasks can continue running (for background-mode components) or run to completion (for batch-mode and interactive-mode components).
You might want to disable an individual component to perform a system maintenance operation outside of the Siebel Server. For example, you might disable the Synchronization Manager component to do a file system reorganization on the docking subdirectory.
To minimize the number of multithreaded processes started on the Siebel Server, you might want to disable components that you do not plan to run.
You might also want to disable components due to database licenses. If you have exceeded the maximum licensed connections for your database, then you might want to disable the Siebel Server components that you plan not to use. You must only disable components for which you do not plan to run tasks across the entire enterprise. Setting the Min MT Servers parameter to 0 for multithreaded Siebel Server components renders the server component unable to run tasks.
An offline component might be set to Online (or Started, if there are still tasks running for the offline component) or Shutdown, in which case, any running tasks are stopped as cleanly as possible.
Shutting Down. Indicates that the Siebel Server component is in the process of shutting down. When this process is complete, the state changes to Shutdown.
Shutdown. Indicates that processes are not running for the component and new tasks might not be started. Each task running when the component shuts down is stopped as soon as possible. Components are set to Shutdown when the Siebel Server shuts down, with the exception of the Siebel Server Manager component, which remains Online to perform administrative commands executed by the Siebel Server Manager. Background-mode components that are set to Shutdown but have a Default Tasks parameter set to a nonzero value might be set to Online or Started.
Unavailable. Indicates that processes are not running for the component when a Siebel Server process is running. Multithreaded Siebel Server components change to an Unavailable component state when the Min MT Servers parameter is set to a value greater than 0 and no Siebel Server processes are actually running for that component. In this case, the Siebel Server component might exit with an error and become unavailable because it failed to initialize. Siebel Server components might also go into this state if the database connection is down. In this case, you must restart the Siebel Server component after the database connection has been reestablished.

Server Component Status Fields

Each server component record has two fields in which the status appears as shown in the following table.

GUI Column Name	Command-Line Interface Column Name	Description
State	CP_DISP_RUN_STATE	The state of the Siebel Server component using the appropriate language code.
State (Icon)	Not applicable	A stoplight icon representing the state of the Siebel Server component. Clicking the icon in the State field reveals the actual state value associated with the stoplight color, which can be one of the following for example: Running or Online (Green stoplight), which indicates normal conditions. Shutting Down (Yellow stoplight), which indicates a temporary non-operational condition. Shutdown or Offline (Red stoplight), which indicates a non-operational condition.

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 about 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. The following table provides the task status fields.

GUI Column Name	Command-Line Interface Column Name	Description
State	TK_RUNSTATE	The state of the task using the appropriate language code.
Status	TK_STATUS	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 icon representing the state of the Siebel Server task. Clicking the icon in the State field reveals the actual state value associated with the stoplight color, which can be one of the following, for example: Running or Completed (Green stoplight), which indicates normal conditions. Paused (Yellow stoplight), which indicates a temporary or non-operational condition. Exited or Exited with Error (Red stoplight), which indicates a non-operational condition.

About Component Job States

After the creation of a component job, it is always in one of the states in the following list. For more information about starting component jobs, see Siebel System Administration Guide. For more information about monitoring component job status, see Monitoring Component Job Status.

Creating. Indicates the component job record is in the process of being defined.
Queued. Indicates the component job record was started and is scheduled to run. The component job field Scheduled Start defines when the component job runs.
Active. Indicates the scheduled component job is running.
On Hold. Indicates the component job is on hold and will not run at the Scheduled Start time. Only component jobs in the queued state can be put on hold.
Cancelled. Indicates the component job is cancelled. Only component jobs in the queued or on hold state can be cancelled.
Canceling. Indicates the component job is in the process of being cancelled.
Error. Indicates the component job ran, but encountered an error during operation.
Success. Indicates the component job ran and completed successfully.
Completed. Indicates that repeating component jobs completed successfully.
Expired. Indicates the component job has expired. The component job field Expiration Date defines when the component job expires.
Parent Request Cancelled. Indicates the first component job of a repeating component job was cancelled. The first component job of a repeating component job is considered the parent job.
Parent Request On Hold. Indicates the first component job of a repeating component job is on hold. The first component job of a repeating component job is considered the parent job.

About User Sessions

User sessions include data on any user logged into the Siebel Server as well as sessions created by the Siebel application. User sessions comprise all interactive component tasks.

User sessions run based on a Siebel Server component task. Therefore, user sessions have the properties of Siebel Server component tasks. The Session ID field of an individual user session shares the same ID number as the Task ID of the component task that runs the session. That is, information about user sessions can be viewed as either a user session or a task.

For information and procedures on monitoring user sessions, see Monitoring User Session Status. For information and procedures on monitoring tasks, see Monitoring Server Component Task Status.

About Siebel Application Statistics

Various statistics are recorded at the task level for every Siebel Server component task. You might use these statistics to:

Monitor the progress and performance of a task, component, or Siebel Server
Optimize system performance

When the task completes its operation, task-level statistics (gathered dynamically during the operation of a task) roll up to the component and Siebel Server levels.

Two types of statistics exist for task-level Siebel Server statistics:

Subsystem statistics. Common to every component process (such as process management, networking, database access, and file I/O) and tracked for each component task.
Component-specific statistics. Only applicable to the component for which the statistics are defined.

When a task for a component completes its operation, both generic and component-specific statistics roll up to the component level. Only generic statistics roll up to the Siebel Server level.

Statistics on the component level includes data for completed tasks on interactive and batch mode components. Statistics for component tasks that are still running are not included. Check the tasks directly to monitor statistics for running tasks on interactive and batch mode components. For information about monitoring task statistics, see Monitoring Server Component Task Statistics. For background mode components, the statistic rollup behavior is slightly different because the component tasks are never complete. For background components, the component statistics change whenever a statistic value is updated by the running component task. For a listing and brief descriptions of Siebel application statistics, see List of Statistics and State Values.

Note: If some Siebel application statistics are not visible, then set the Show Advanced Objects (alias ShowAdvancedObjects) parameter to TRUE for the server component Server Manager (alias ServerMgr). For more information about advanced objects, see Siebel System Administration Guide.

About Siebel Application State Values

State values contain information about the current operation of a task or the component for which the task is running. Component tasks periodically update their state values to indicate information about their current processing, such as the current phase of operation. State values are defined at the component and task levels. Component-level state values refer to the state of the component as a whole. Task-level state values refer to the state of an individual process for a Siebel Server component.

Two types of state values exist for components and component tasks:

Subsystem state values. Kept for every component (such as Component Start Time and Component Stop Time) and component task (such as Task Start Time and Task Stop Time) that uses that subsystem.
Component-specific state values. Kept for every component and component task. Only applicable to the component for which they are defined.

Monitoring Siebel Enterprise Server Status

Monitor the status of Siebel Servers in a Siebel Enterprise Server by using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr). For configuration tasks and background information about the Siebel Enterprise Server, see Siebel System Administration Guide.

To monitor a Siebel Enterprise Server using the Server Manager GUI

Navigate to the Administration - Server Management screen, Enterprises, and then the Servers view.
The following information appears:
- The name and description of the Siebel Enterprise Servers available are in the Enterprise Servers list.
- The state of the Siebel Servers for the selected Siebel Enterprise Server are available in the Servers list. For details on Siebel Server states, see About Siebel Server States.
- The state of the Siebel Server components for the selected Siebel Server are available in the Components list. For details on Siebel Server component states, see About Siebel Server Component States.

To monitor Siebel Enterprise Server using srvrmgr

At the srvrmgr program prompt, enter:
```
list servers
```

Caution: Make sure you do not start the Server Manager command-line interface program for a particular Siebel Server; that is, do not start the Server Manager command-line interface with the /s flag.

For details on starting, running, and configuring the Server Manager command-line interface program, see Siebel System Administration Guide.

Monitoring Siebel Server Status

Monitor the status of Siebel Servers by using the Server Manager GUI or Server Manager command-line interface program (srvrmgr program). The following topics describe procedures that monitor the Siebel Server:

For background information about Siebel Servers, including running and configuring procedures, see Siebel System Administration Guide.

Monitoring Siebel Server State

Monitor the status of a Siebel Server by using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr). For details on the possible states of the Siebel Server, see About Siebel Server States. For information about monitoring other Siebel Server run-time operations, see Monitoring Siebel Server Status.

To monitor the Siebel Server state using the Server Manager GUI

Navigate to the Administration - Server Management screen, then Servers view.
In the Servers list, select the Siebel Server of interest.
Review the state of the selected Siebel Server by viewing the State (Icon) or Server State fields.

To monitor the Siebel Server state using srvrmgr

At the srvrmgr program prompt, enter:
```
list servers
```

For details on starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.

Monitoring Siebel Server Component Groups

Monitor the status of component groups for a Siebel Server using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr). For details on Siebel Server component group states, see About Siebel Server Component Group States. For information about monitoring other Siebel Server run-time operations, see Monitoring Siebel Server Status.

To monitor component groups using Server Manager GUI

Navigate to the Administration - Server Management screen, then Servers view.
In the Servers list, select the Siebel Server of interest.
From the view tabs, click Component Groups.
Review the state of the component groups for the selected Siebel Server by viewing the State (Icon) and State fields of each component group record.

To monitor component groups on srvrmgr

At the srvrmgr program prompt, enter

list component groups for server siebel_server_name

For details on starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.

Monitoring Siebel Server Log Files

Monitor the log files for a Siebel Server using the Server Manager GUI. You can also review Siebel Server log files by manually accessing the file or querying the file with the Log File Analyzer (LFA) utility.

For background information about:

Siebel Server log files, see About Siebel Server Log Files.
LFA, see About the Log File Analyzer.
Event logging, see About Configuring Siebel Server and Component Logging.

For information about monitoring other Siebel Server run-time operations, see Monitoring Siebel Server Status.

To monitor Siebel Server log files on Server Manager GUI

Navigate to the Administration - Server Management screen, then Servers view.
In the Servers list, select the Siebel Server of interest.
From the view tabs, click Log.
Each entry in the Log view list represents an event logged in the Siebel Server log file. For more details on each entry, click the record of interest and review information in the Info Detail view.

Note: The Server Manager GUI accesses Siebel Server log files from the log directory of each individual Siebel Server. Siebel Server log files use the following name convention: EnterpriseServerName. SiebelServerName.log.

Monitoring Siebel Server Statistics

Monitor Siebel Server statistics using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr). For background information and a list of Siebel Server statistics, see List of Statistics and State Values. For information about monitoring other Siebel Server run-time operations, see Monitoring Siebel Server Status.

To monitor Siebel Server statistics on Server Manager GUI

Navigate to the Administration - Server Management screen, then Servers view.
In the Servers list, select the Siebel Server of interest.
From the view tabs, click Statistics.
Statistics for the selected Siebel Server appear in the Statistics list. For a list and description of Siebel Server statistics, see List of Statistics and State Values.

To monitor Siebel Server statistics on srvrmgr

At the srvrmgr program prompt for a particular Siebel Server, enter:
```
list statistics for server siebel_server_name 
```

For details on starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.

Monitoring Siebel Server Tasks

Monitor Siebel Server component tasks for a particular Siebel Server by using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr).

For details on Siebel Server component task states, see About Siebel Server Task States. For information about monitoring other Siebel Server run-time operations, see Monitoring Siebel Server Status.

To monitor Siebel Server tasks on Server Manager GUI

Navigate to the Administration - Server Management screen, then Servers view.
In the Servers list, select the Siebel Server of interest.
From the view tabs, click Tasks.
Review the status of the tasks for the selected Siebel Server by viewing the State (Icon), State, and Status fields.

For more information about monitoring individual tasks, note the Task number and see Monitoring Server Component Task Status.

To monitor Siebel Server tasks on srvrmgr

At the srvrmgr program prompt, enter:

list tasks for server siebel_server_name

For details on starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.

Monitoring Siebel Server User Sessions

Monitor user sessions for a particular Siebel Server by using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr).

For background information about user sessions, see About User Sessions. For information about monitoring other Siebel Server run-time operations, see Monitoring Siebel Server Status.

To monitor Siebel Server user sessions on Server Manager GUI

Navigate to the Administration - Server Management screen, then Servers view.
In the Servers list, select the Siebel Server of interest.
From the view tabs, click Sessions.
Review the status of the users’ sessions for the selected Siebel Server by viewing the State (Icon), Task Hung State, and State fields.

For more details on monitoring individual user sessions, note the Session ID number and see Monitoring User Session Status.

To monitor Siebel Server user sessions on srvrmgr

At the srvrmgr program prompt, enter:

list sessions for server siebel_server_name

For details on starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.

Monitoring Siebel Server Component Status

Monitor the status of Siebel Server components by using the Server Manager GUI or Server Manager command-line interface program (srvrmgr). The following topics describe procedures that monitor the Siebel Server components:

For background information about Siebel Server components, including running and configuring procedures, see Siebel System Administration Guide.

Monitoring Siebel Server Component State

Monitor the status of Siebel Server components using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr).

For details on Siebel Server component states, see About Siebel Server Component States. For information about monitoring other Siebel Server component run-time operations, see Monitoring Siebel Server Component Status.

To monitor the Siebel Server component state on Server Manager GUI

Navigate to the Administration - Server Management screen, then Components view.
In the Components list, select the Siebel Server component of interest.
Review the state of the selected Siebel Server component by viewing the State (Icon) and State fields.

The Components list view lists the Siebel Server components from all Siebel Servers operating in the Siebel Enterprise Server.

To monitor the component state on srvrmgr

At the srvrmgr program prompt, enter:
```
list component
```

For details on starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.

Monitoring Siebel Server Component State Values

Monitor Siebel Server component state values using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr). For background information and a list of Siebel Server state values, see List of Statistics and State Values. For information about monitoring other Siebel Server component run-time operations, see Monitoring Siebel Server Component Status.

To monitor component state values on Server Manager GUI

Navigate to the Administration - Server Management screen, then Components view.
In the Components list, select the Siebel Server component of interest.
From the view tabs, click State Values.
State values for the selected Siebel Server component appear in the State Values list. For a list and description of Siebel Server state values, see List of Statistics and State Values.

To monitor component state values on srvrmgr

At the srvrmgr program prompt, enter:

list state values for component component_alias_name

For details on starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.

Monitoring Siebel Server Component Statistics

Monitor Siebel Server component statistics using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr). For background information and a list of Siebel Server component statistics, see List of Statistics and State Values. For information about monitoring other Siebel Server component run-time operations, see Monitoring Siebel Server Component Status.

To monitor component statistics on Server Manager GUI

Navigate to the Administration - Server Management screen, then Components view.
In the Components list, select the Siebel Server component of interest.
From the view tabs, click Statistics.
Statistics for the selected Siebel Server component appear in the Statistics list. For a list and description of Siebel Server statistics, see List of Statistics and State Values.

To monitor component statistics on srvrmgr

At the srvrmgr program prompt, enter:

list statistics for component component_alias_name

For details on starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.

Monitoring Siebel Server Component Tasks

Monitor tasks for a particular Siebel Server component by using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr). For details on Siebel Server component task states, see About Siebel Server Task States. For information about monitoring other Siebel Server run-time operations, see Monitoring Siebel Server Status.

To monitor Siebel Server tasks on Server Manager GUI

Navigate to the Administration - Server Management screen, then Components view.
In the Components list, select the Siebel Server component of interest.
From the view tabs, click Tasks.
Review the status of tasks for the selected Siebel Server component by viewing the State (Icon), State, and Status fields.

For more details on monitoring individual tasks, note the Task number and see Monitoring Server Component Task Status.

To monitor component tasks on srvrmgr

At the srvrmgr program prompt, enter:

list tasks for component component_alias_name

For details on starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.

Monitoring Server Component Task Status

Monitor the status of Siebel Server component tasks by using the Server Manager GUI or Server Manager command-line interface program (srvrmgr). The following topics describe procedures that monitor Siebel Server component tasks:

A task, in the context of a Siebel application, is an instantiation of a Siebel Server component. Administrators start tasks by creating jobs. Tasks are also started by the Siebel application itself. For background information about Siebel Server component tasks, including running and configuring procedures, see Siebel System Administration Guide.

Monitoring Server Component Task State

Monitor the state of Siebel Server component tasks using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr). For details on Siebel Server component task states, see About Siebel Server Task States. For information about monitoring other task run-time operations, see Monitoring Server Component Task Status.

To monitor tasks on Server Manager GUI

Navigate to the Administration - Server Management screen, then Tasks view.
In the Tasks list, select the task of interest.
Review the state of the selected task by viewing the State (Icon), State, and Status fields.

The Tasks view lists tasks from all Siebel Servers operating in the Siebel Enterprise Server. To isolate tasks on a particular Siebel Server, see Monitoring Siebel Server Tasks. To isolate tasks for a particular Siebel Server component, see Monitoring Siebel Server Component Tasks.

Note: You cannot sort tasks from different Siebel Servers across the enterprise.

To monitor tasks on srvrmgr

At the srvrmgr program prompt, enter:
```
list tasks
```

For details on starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.

To list tasks that have exited in error

Make sure that the SvrTaskPersist component (which belongs to the SystemAux component group) is enabled.
Run an SQL statement to query tasks that exit in error for a specific table.
For example, you might use the following query to return tasks with errors from the S_SRM_TASK_HIST table:
```
select CREATED, SRVR_PROC_ID_VAL, SRVR_LOGFILE_NAME, SRVR_STATUS
  from SIEBEL.S_SRM_TASK_HIST
  where SRVR_TASK_ID_VAL='123456789';
```
All tasks that exited in error are returned by the SQL statement with the status set to ERROR.

Monitoring Server Component Task Log Files

Monitor the log files for a Siebel Server component task using the Server Manager GUI. Also review task log files by manually accessing the file or querying the file with the Log File Analyzer (LFA) utility.

For background information about:

Event logging, see Configuring Siebel Server and Component Logging.
Task log files, see Configuring Siebel Server Component Logging.
LFA, see Querying System Log Files.

For information about monitoring other task run-time operations, see Monitoring Server Component Task Status.

To monitor task log files on Server Manager GUI

Navigate to the Administration - Server Management screen, then Tasks view.
In the Tasks list, select the task of interest.
From the view tabs, click Log.
Each entry in the Log view list represents an event logged in the task log file.

Monitoring Server Component Task State Values

Monitor Siebel Server component task state values using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr). For background information and a list of task state values, see . For information about monitoring other task run-time operations, see Monitoring Server Component Task Status.

To monitor task state values on Server Manager GUI

Navigate to the Administration - Server Management screen, then Tasks view.
In the Tasks list, select the task of interest.
From the view tabs, click State Values.
State values for the selected task appear in the State Values list. For a list and description of task state values, see List of Statistics and State Values.

To monitor task state values on srvrmgr

At the srvrmgr program prompt, enter:
```
list state values for task task_number
```

For details on starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.

Monitoring Server Component Task Statistics

Monitor Siebel Server component task statistics using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr). For background information and a list of task statistics, see List of Statistics and State Values. For information about monitoring other task run-time operations, see Monitoring Server Component Task Status.

To monitor task statistics on Server Manager GUI

Navigate to the Administration - Server Management screen, then Tasks view.
In the Tasks list, select the task of interest.
From the view tabs, click Statistics.
Statistics for the selected task appear in the Statistic list. For a list and description of task statistics, see List of Statistics and State Values.

To monitor task statistics on srvrmgr

At the srvrmgr program prompt, enter:
```
list statistics for task task_number
```

For details on starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.

Monitoring Component Job Status

Monitor the status of Siebel Server component jobs using the Server Manager GUI. For background information about starting Siebel Server component jobs, see Siebel System Administration Guide. For information about component job states, see About Component Job States.

To monitor component job status

Navigate to the Administration - Server Management screen, then Jobs view.
In the Jobs list, select the component job of interest.
Review the status of the component job by viewing the Status field.

To monitor component job status requested by your User ID

Navigate to the Jobs screen.
In the My Jobs list, select the component job of interest.
Review the status of the component job by viewing the status field.

Monitoring User Session Status

Monitor the status of user sessions by using the Server Manager GUI or Server Manager command-line interface program (srvrmgr). The following topics describe procedures that monitor user sessions:

For background information about user sessions, see About User Sessions.

Monitoring User Session State

Monitor the state of Siebel Server user sessions using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr). The state of the user session is that of the associated Siebel Server component task that represents the user session.

For background information about user sessions, see About User Sessions. For background information about Siebel Server component task states, see About Siebel Server Task States. For information about monitoring other Siebel Server user session run-time operations, see Monitoring User Session Status.

To monitor user sessions on Server Manager GUI

Navigate to the Administration - Server Management screen, then Sessions view.
In the Sessions list, select the Siebel Server user session of interest.
Review the state of the selected Siebel Server user session by viewing the State (Icon), Task Hung State, and State fields.

The Sessions view lists Siebel Server user sessions from all Siebel Servers operating in the Siebel Enterprise Server. To isolate sessions on a particular Siebel Server, see Monitoring Siebel Server Tasks.

To monitor user sessions for a Siebel Server using srvrmgr

At the srvrmgr program prompt, enter:

list sessions for server siebel_server_name

At the srvrmgr program prompt, enter:

list sessions for comp component_alias_name

At the srvrmgr program prompt, enter:

list sessions for login object_manager_login

At the srvrmgr program prompt, enter:

list hung sessions for server siebel_server_name [or]comp component_alias_name
[or]login object_manager_login

At the srvrmgr program prompt, enter:

list active sessions for server siebel_server_name [or]comp component_alias_name
[or]login object_manager_login

For more information about starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.

Monitoring User Session Log Files

Monitor the log files for Siebel Server user sessions using the Server Manager GUI. User session log files are those of the associated Siebel Server component task that represents the user session. Also review Siebel Server user session log files by accessing the associated task log file or querying the associated task log file with the Log File Analyzer utility.

For background information about:

User sessions, see About User Sessions.
Siebel Server component task log files, see Configuring Siebel Server Component Logging.
Log File Analyzer, see Querying System Log Files.
Event logging, see Configuring Siebel Server and Component Logging.

For information about monitoring other Siebel Server user session run-time operations, see Monitoring User Session Status.

To monitor user session log files on Server Manager GUI

Navigate to the Administration - Server Management screen, then Sessions view.
In the Sessions list, select the Siebel Server user session of interest.
From the view tabs, click Log.
Each entry in the Log view represents an event logged in the Siebel Server component task log file, which represents the user session.

Monitoring User Session State Values

Monitor Siebel Server user session state values using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr). User session state values are those of the associated Siebel Server component task that represents the user session.

For background information about user sessions, see About User Sessions. For background information and a list of task state values, see List of Statistics and State Values. For information about monitoring other Siebel Server user session run-time operations, see Monitoring User Session Status.

To monitor user session state values on Server Manager GUI

Navigate to the Administration - Server Management screen, then Sessions view.
In the Sessions list, select the Siebel Server user session of interest.
From the view tabs, click State Values.
State values for the selected task that represent the user session appear in the State Values list. For a list and description of task state values, see List of Statistics and State Values.

To monitor user session state values on srvrmgr

Use the srvrmgr command to list task state values as described in Monitoring Server Component Task State Values. Use the Session ID for the task number parameter in this command.

Monitoring User Session Statistics

Monitor Siebel Server user session statistics using the Server Manager GUI or the Server Manager command-line interface program (srvrmgr). User session statistics are those of the associated Siebel Server component task that represents the user session.

For background information about user sessions, see About User Sessions. For background information and a list of task statistics, see List of Statistics and State Values. For information about monitoring other Siebel Server user session run-time operations, see Monitoring User Session Status.

To monitor user session statistics on Server Manager GUI

Navigate to the Administration - Server Management screen, then Sessions view.
In the Sessions list, select the Siebel Server user session of interest.
From the view tabs, click Statistics.
State values for the selected task that represent the user session appear in the State Values list. For a list and description of task state values, see List of Statistics and State Values.

To monitor user session statistics on srvrmgr

Use the srvrmgr command to list task statistics as described in Monitoring Server Component Task State Values. Use the Session ID for the task number parameter in this command.

Analyzing System Data with Siebel Run-Time Data

Analyze operating system data with Siebel run-time data using the following procedures.

Identifying Task Log Files From the Siebel Server Log File

Map the Siebel Server log file to its Siebel Server components and their log files by identifying the task ID in the Siebel Server log file. Review the task log file for more information about the task performance.

Note: The detail of the log file depends on logging levels set for event types for each component. For details on event types and event logging, see Configuring Siebel Server and Component Logging.

For information about analyzing other Siebel application diagnostic data, see Analyzing System Data with Siebel Run-Time Data.

To identify task IDs from Siebel Server log files

Access a Siebel Server log file by using the Server Manager GUI. For details on this procedure, see Monitoring Siebel Server Log Files.
Also access Siebel Server log files by:
- Using the Log File Analyzer. For details on this procedure, see Querying System Log Files.
- Opening the log file itself. For details on locations and naming convention of Siebel Server log files, see About Siebel Server Log Files.
Review the Text field of each log file entry for the Siebel Server component of interest.
The text field of each Siebel Server component log file entry also contains the task ID number started for this component.
Access the Siebel Server component task list. For details on this procedure, see Monitoring Server Component Task State.
Query the list with the task ID number identified in the Siebel Server log file.
Review the status of the Siebel Server component task by reviewing the log file, state value, and statistics for this task. For details on these procedure, see Monitoring Server Component Task Status.

Note: The task ID number identified in Step 3 can also be used to find the individual task log file stored in the log directory. The name of the task log file contains the task ID for the component. For example, in SCCObjMgr_enu_19369.log, the task ID is 19369.

Process of Mapping Tasks with Operating System Data

Mapping tasks to operating system data allows you to view operating system CPU and memory usage for each task. Once you map a task to an operating system process ID, you can use operating system tools, such as task manager on Windows or the ps (process list) function on UNIX systems, to view other information about the process and task including CPU utilization, memory usage, and so on.

Note: Multithreaded components can have several tasks mapped to a single operating system process ID, so that the operating system tools do not necessarily break down the data by task.

Map the Siebel Server component task to the operating system data by:

Identifying the operating system process ID (PID) for a task. For this procedure, see Identifying Operating System PID for a Task.
Reviewing the PID in the operating system. For this procedure, see Identifying Operating System PID for a Task.

For information about analyzing other Siebel application diagnostic data, see Analyzing System Data with Siebel Run-Time Data.

Identifying Operating System PID for a Task

Identifying operating system PID numbers is a task in the Process of Mapping Tasks with Operating System Data. Identify operating system process ID numbers (PID) for tasks by one of the following methods:

From the Server Manager GUI
From the Siebel Server log file
From the Task log file

Note: PIDs are only available in the Server Manager for running tasks.

To identify operating system PID for a task from the Server Manager GUI

Access the Siebel Server component task list. For details on this procedure, see Monitoring Server Component Task State.
Query the task list for a specific Siebel Server component task or task ID.
Note the value in the PID field for that particular task.

To identify operating system PID for a task from a Siebel Server log file

Access a Siebel Server log file by using the Server Manager GUI. For details on this procedure, see Monitoring Siebel Server Log Files.
Also access Siebel Server log files by:
- Using the Log File Analyzer. For details on this procedure, see Querying System Log Files.
- Opening the log file itself. For details on locations and naming convention of Siebel Server log files, see About Siebel Server Log Files.
Review the Text field of each log file entry for the Siebel Server component of interest.
The Text field of each Siebel Server component log file entry also contains the process ID number started for this component task.

To identify operating system PID for a task from a task log file

Access the Siebel Server component task log file of interest. For details on locations and naming convention of Siebel Server component task log files, see Configuring Siebel Server and Component Logging.
The first entry of the task log file contains the header information. The header information contains the PID number. For a parsing of the header file and to identify the PID number, see About Event Attributes and Log File Format.

Reviewing the PID in the Operating System

Reviewing the process ID number in the operating system allows the identification of CPU and memory usage for individual tasks. To identify the PID number for a task, see Identifying Operating System PID for a Task.

Reviewing the PID numbers in the operating system is a task in the Process of Mapping Tasks with Operating System Data.

To review PID numbers under Microsoft Windows

Using the right mouse button, click a blank area on the taskbar.
Choose Task Manager.
The Windows Task Manager dialog box appears.
Select the Processes tab and query for the task PID number.

Note: If the PID column is not visible, then click View, then Select Columns.

To review PID numbers under UNIX

Enter the command:
```
ps -ef | grep PID
```
or:
```
ps -aux PID
```
In this command, PID is the process ID number of interest.

Mapping User Sessions to Siebel Servers or Application Object Managers

Map user sessions from the Siebel Application Interface to individual Siebel Servers or Siebel Application Object Managers by accessing the user session cookie in the Siebel Application Interface log file. For information about analyzing other Siebel application diagnostic data, see Analyzing System Data with Siebel Run-Time Data.

To map user session to a Siebel Server

Access the Siebel Application Interface log file. For details on locations and naming convention of the Siebel Application Interface log file, see Configuring Siebel Server and Component Logging.
Start the Server Manager command-line interface program (srvrmgr) at the enterprise level.
For information about starting and running srvrmgr, see Siebel System Administration Guide.

Enter the following command:

list servers show SBLSRVR_NAME, SV_SRVRID

Access the Siebel Application Interface log file. For details on locations and naming convention of the Siebel Application Interface log file, see Configuring Siebel Server and Component Logging.
Access the Siebel Server component task list. For details on this procedure, see Monitoring Server Component Task State.
Query the task list for the specific PID to isolate the Application Object Manager task for that user session.
Review data on that Application Object Manager task.

For details on these procedures, see Monitoring Server Component Task Status.

About Using SQL Tagging to Trace Long-Running Queries in Siebel CRM

The SQL tagging feature in Siebel CRM provides administrators with the ability to trace the origin of long-running or slow-performing SQL statements (queries) back to a specific task and user who triggered it. This topic describes the SQL tagging feature and syntax. It also provides sample code.

After SQL tagging is enabled, tagging information is added to the SELECT statements that are generated by the Siebel Application Object Manager. When a poorly performing SQL statement is suspected, the database administrator can use this tagging information at the database level to trace which component task and user initiated the SQL without the need to reboot any Siebel Server or components. Database administrators can then find the component task log file for more in-depth analysis of the performance issue. For information about enabling SQL tagging, see Enabling and Disabling SQL Tagging.

Note: Other SQL statements generated by Siebel Application Object Manager, such as INSERT, UPDATE, and DELETE, are not tagged.

SQL Tagging Format

SQL tagging information is formatted as a comma-separated list of values using the following syntax:

componentname,servername,taskid,userid,flowid:sarmid,busobjname,buscompname,viewname

where:

componentname is the alias of the component, for example, SCCObjMgr_enu.
servername is the name of the Siebel Server on which the component or task is running.
taskid is the task ID of the user who generated the query.
userid is the login name of the user who generated the query.
flowid is the flow ID of the component or task.
sarmid is the SARM ID of the component or task.
busobjname is the business object name.
buscompname is the business component name.
viewname is the view name (only in UI mode).

Note: Any optional elements of a tag that are irrelevant or missing for the query are replaced with an empty string.

Sample SQL-Tagged Code

The following is a sample of how a tagged SQL statement might appear in a log file when the SQL statement was generated from a Siebel Call Center (SCCObjMgr_enu) Application Object Manager component and an Oracle database. The changes made by the SQL tagging feature appear in italics.

SELECT
	FIRST_NAME,
	LAST_NAME,
 	...,
:1
FROM 
	TBO.S_CONTACT
...
WHERE 
	LAST_NAME LIKE:2
ORDER BY
...
Bind variable 1: 
SCCObjMgr_enu,sdchs20i046,10485776,SADMIN,00000089489108a8:50557,Account,Account,
Account List View
Bind variable 2: Foo*

For information about enabling SQL tagging, see Enabling and Disabling SQL Tagging. For information about setting log levels for SQL tagging, see Setting Log Levels for SQL Tagging.

Enabling and Disabling SQL Tagging

The SQL tagging feature in Siebel CRM is a diagnostic tool that allows administrators to trace long-running or slow-performing queries back to the user or action that triggered it. For more information about SQL tagging, see About Using SQL Tagging to Trace Long-Running Queries in Siebel CRM.

By default, SQL tagging is disabled. Administrators can enable SQL tagging by setting the OM SQL Tagging (alias is ObjMgrSqlTag) server component event for a Siebel Application Object Manager server component, such as Call Center Object Manager (ENU). The OM SQL Tagging event is available to all object manager-based components, such as AppObjMgr, EAIObjMgr, BusSvcMgr, and so on. You can enable and disable SQL tagging at any time if the Application Object Manager server component is running.

Enabling SQL Tagging

Use the following procedure to enable SQL tagging.

To enable SQL tagging

Navigate to the Administration - Server Configuration screen, then the Components view.
In the Components list, select the appropriate Siebel Application Object Manager for the application that you want to enable SQL tagging.
For example, if the application you are using is Siebel Call Center, then select Call Center Object Manager (ENU).
Click the Events subview, and then select the OM SQL Tagging event type.
Set the log level to a number greater than 1 (one).
For more information about setting the log levels, see Setting Log Levels for SQL Tagging.

Disabling SQL Tagging

Use the following procedure to disable SQL tagging.

To disable SQL tagging

Navigate to the Administration - Server Configuration screen, Components view.
In the Components list, select a Siebel Application Object Manager, for example, Call Center Object Manager (ENU).
Click the Events subview, and then select the OM SQL Tagging event type.
Set the log level to 1 (one).

About Setting Log Levels for SQL Tagging

The Object Manager SQL Log (alias ObjMgrSqlLog) server component event type has an SqlTag event subtype. The SqlTag subtype sets the log level for an SQL tag at a lower lever than where SQL statements are typically logged. It enables logging of the SQL tags in the log file without logging the complete SQL statements.

The OM SQL Logging (ObjMgrSqlLog) and OM SQL Tagging (ObjMgrSqlTag) events are independent of each other and can coexist. The ObjMgrSqlLog event controls the level of SQL logging detail in an object manager log file. The ObjMgrSqlTag event controls whether SQL statements are tagged or not and how much tagging information is generated, irrespective of whether or not the SQL statements are logged in the log file. For example, if the ObjMgrSqlLog event log level is set to 1, then neither the SQL statements nor the SQL tags are logged in the log files, even if the ObjMgrSqlTag subevent is active. Whereas, if the ObjMgrSqlLog event log level is set to 4, then full details about the SQL information is generated in the log files. However, if the ObjMgrSqlTag subevent is not active, then the SQL is not tagged, nor are the SQL tags logged in the log files.

If SQL tagging is active and the SQL Logging event is set at the SqlTag level, then only the SQL tags are logged in the log files as shown in the following example:

Begin: Execute SqlObj 'Account' at 11160f10 with 
SqlTag=SCCObjMgr_enu,sdchs20i046,10485776,,SADMIN,00000089489108a8:50557,
Account,Account,Account List V

This configuration is useful in diagnosing long-running SQLs without generating too much SQL logging in the log files.

Note: The END statement is logged so that you can run a script to identify log files where the BEGIN SQL tag statement is present, but there is no END statement. This syntax helps determine which log files might contain long-running SQL statements.

For information about setting log levels for SQL tagging, see Setting Log Levels for SQL Tagging.

Setting Log Levels for SQL Tagging

The OM SQL Tagging (ObjMgrSqlTag) server component event controls whether SQL tagging is enabled and how much tagging information is generated. Event log levels (event subtypes) control the level of detail that is added to each tag. The higher the log level, the higher the level of detail. For more information about setting SQL tagging log levels, see About Setting Log Levels for SQL Tagging.

To set the log level for SQL tagging

Navigate to the Administration - Server Configuration screen, then the Components view.
In the Components list, select the appropriate Siebel Application Object Manager for the application that you want to enable SQL tagging.
For example, if the application you are using is Siebel Call Center, then select Call Center Object Manager (ENU).
Click the Events subview, and then select the OM SQL Tagging event type.

Change the log level to a number using the following guidelines.

Log Level	Description
0	SQL tagging is disabled.
1	SQL tagging is disabled.
2	SQL tagging includes only the component name, server name, and task ID. Note: Use this log level when you do not want user IDs exposed in an SQL Tagging event log for an Application Object Manager.
3	SQL tagging includes the component name, server name, task ID, user ID, and flow ID with the SARM ID.
4	SQL tagging includes the component name, server name, task ID, user ID, and flow ID with the SARM ID, business object, business component, and view name.

About Siebel Process Failure Diagnostics

Siebel CRM provides process failure diagnostics that help you to allocate system resources and maintain an efficient and reliable environment. Administrators can monitor KPIs (key performance indicators) of the various levels of the Siebel environment to do the following:

Identify, isolate, and remedy adverse system and application conditions.
Adjust the various settings and parameters of the Siebel environment to avert adverse conditions.
Optimize available resources for improved performance.

When a Siebel process fails, the administrator can do the following:

View all detectable failed processes for a given Siebel Enterprise by Siebel Server.
Identify the probable cause and point of origin of the failure, including (but not limited to) user, process, thread, task, application, view, and activity immediately prior to the failure.
Review content of the main process failure file (crash.txt) associated with a given failure including the call stack, the register contents, and the memory information.
Review content of other failure information contained in the Siebel FDR (Flight Data Recorder), Siebel ARM (Application Response Measurement), and component log files.
Determine other Siebel users directly affected by the failure.

How Siebel Process Failure Diagnostics Work

Siebel process failure diagnostics collects data for use by administrators to diagnose and troubleshoot a variety of failed Siebel Server processes.

The SvrTaskPersist component of the SystemAux component group handles the diagnostic data collection. This component uses the SIEBEL_DIAG_STORE environment variable as a location store to retrieve the diagnostic data (FDR file, crash.txt file, component log file, failure summary, and so on).

The administrator can use the siebprocdiag command-line utility to output the process failure data to any path you specify for future retrieval. The utility scans the SIEBEL_ROOT\siebsrvr\bin directory and collects the various files for each process failure and copies them to the specified directory. For example, if you execute the following command for Windows, then the process failure files are copied to d:\temp:

siebprocdiag d:\temp

For information about configuring system environment variables and using server management utilities, see Siebel System Administration Guide.

Scenario for Working with Siebel Process Failure Diagnostics

This topic provides a scenario for working with Siebel Process Failure Diagnostics. You might use this feature differently, depending on your business needs.

An administrator is informed by a user that the Siebel application is unresponsive. The administrator navigates to the Process Failure Diagnostics view to investigate whether the cause might be a failed process. After identifying a failed process that is associated with that user, the administrator can view the details of the failure including:

Siebel Server and server component names
Time of failure
Process, thread, and task IDs
Number of affected tasks
Last set of meaningful business processes that occurred at the time of the failure
Whether a new process was created, and if so, the list of current users impacted by the failure
A list of users whose sessions were lost following the failure
Content of the actual crash.txt file that was logged, which provides the call stack, register contents, and memory information

The administrator then determines the cause and effect to address the issue or investigates further to resolve. When applicable, the administrator forwards the details to an internal technical support team to assist them in their troubleshooting activities. The administrator might also want to query the failed process data in the Siebel database to generate histograms or reports to initiate preventative measures.

Investigating Failed Siebel Server Processes

The process failure feature in Siebel CRM provides administrators with the ability to analyze and diagnose various system failures. Administrators can identify the following:

Siebel Server and component process or processes that have failed
Users who have lost sessions as a result of the process failure
User actions that might have resulted in the failure
Dump files associated with the failed process

To investigate a failed Siebel Server process

Navigate to the Administration - Server Management screen, Diagnostics, and then the Process Failure Diagnostics view.
In the Failed Processes list, select a record to view the Siebel Server, server component, failure time, and other details about the process that failed.
In Affected Users on Failed Process, view the users who have lost the sessions as result of the process failure.
In Failed User Task, view the user actions that might have resulted in the failure.
In Failed Process Call Stack, view the content of the crash.txt file, which is the call stack information.

If you need further assistance with troubleshooting, then create a service request (SR) on My Oracle Support. Alternatively, you can phone Oracle Global Customer Support directly to create a service request or get a status update on your current SR. Support phone numbers are listed on My Oracle Support.

Example of Investigating a Failed Siebel Server Process

This topic gives one example of how you might investigate a failed Siebel Server process. You might use this feature differently, depending on your business needs. When a Siebel Server process failure is suspected, administrators can diagnose the nature of the failure in detail.

To investigate a failed Siebel Server process

Navigate to the Administration - Server Management screen, then the Process Failure Diagnostics view.
In the Failed Process list, select the failed process for which you want to learn more, then review the details about that failure. Details include: the Siebel Server and server component on which the process failed; the time of failure; process, thread, and task IDs; the location of related failure dump files, and so on.
Identify all users associated with this task, and notify these users as appropriate, that a key process related to their current activity has failed. Both the administrator and users can then take appropriate action, such as restarting any operations that have halted because of the failed process.
Review the activity and events (user-initiated and otherwise) that occurred immediately prior to the process failure.
Administrators can use this information to detect patterns in Siebel configurations, usage, and interdependencies of Siebel entities (components, attribute and parameter settings, hardware, and so on) that might lead to process failures.
Query the failed process data in the Siebel database to generate histograms and reports. If the data indicates that failures are related to resources or throughput, then administrators can use that data for potential preventative measures.
Forward details from failure-related files and detectable patterns to technical support to assist in their troubleshooting of code and configuration issues.