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

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.

Related Topics

About Siebel Process Failure Diagnostics

How Siebel Process Failure Diagnostics Work

Investigating Failed Siebel Server Processes

Example of Investigating a Failed Siebel Server Process