Foglight for Siebel 5.2.1 - User and Reference Guide

The Sieb_Comp_State rule determines when Siebel Components other than Transaction Router, Transaction Merger, and Transaction Processor are not currently online or running.

SiebelServer_SiebelComponents

A Siebel component can be in one of five states: Running, Online, Offline, Shutdown, or Unavailable. The Siebel component state definitions are:

Table 26. Sieb_Comp_State rule definition
Condition	State	Action
(scope.get("ComponentAlias") != "TxnMerge" && scope.get("ComponentAlias") != "TxnProc" && scope.get("ComponentAlias") != "TxnRoute") && (#ComponentState# != "Running" && #ComponentState# != "Online")	Critical	Log message, email Siebel administrator

Interpreting the rule

•

Running—indicates that tasks are currently running for the 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, all background mode components for which processes are started by default (that is, components with a Default Tasks parameter set to a nonzero value) start.

•

Online—indicates that tasks are currently not running for the server component, but new tasks may be started through the Siebel Server Manager. New tasks can also start in response to client requests, for interactive-mode components. When the Siebel Server starts, all components for which processes are not started by default are online. When a new task is started for the component, the component state changes to Starting Up.

•

Offline—indicates that new tasks may 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).

•

Shutdown—indicates that processes are not running for the component and new tasks may not be started. Each task running when the component shuts down is stopped as soon as possible. All components are set to Shutdown when the Siebel Server shuts down, with the exception of the Server Manager component, which remains Online in order 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 may be set to Online or Started.

•

Unavailable—indicates that processes are not running for the component when a server process should be running. Multi-threaded server components can go into an Unavailable component state when the Min MT Servers parameter is set to a value greater than zero and no server processes are actually running for that component. In this case, the server component may exit with error and become unavailable because it failed to initialize. Server components may also go into this state if the database connection is down. In this case, you need to restart the server.

The Sieb_Comp_State:CRITICAL alert is raised when a Siebel component other than Transaction Router, Transaction Merger, and Transaction Processor are not ‘Online’ or ‘Running’. If the Siebel administrator has not intentionally stopped the Siebel component, the Siebel administrator should start the Siebel component with the Siebel Server Manager.

Views that render data that this rule is based on:

•

Sieb_Comp_Availability graph view .

Sieb_Crash_Log rule

The Sieb_Crash_Log rule determines if a Siebel object manager crash log has been created. The creation of the log signals that an object manager crashed, causing the users who are currently using the crashed object manager to encounter a service interruption.

SiebelServer_SiebelLogMsg

In Siebel 7 enterprises, when the object managers crash, a crash log is created in the SIEBEL_HOME/bin directory. The existence of a new crash log signals that an object manager has crashed.

Table 27. Sieb_Crash_Log rule definition
Condition	State	Action
SiebelServer.SiebelLogMsg.Severity=="CRASHLOG"	Warning	Log message

Interpreting the Rule

The Sieb_Crash_Log:WARNING alert indicates that the SiebelServer Agent detects a new crash log during the last refresh interval. The Siebel administrator can use the crash log to determine which object manager task crashed and correlate how many users are affected by the crash. Siebel Support can be contacted for help in deciphering the crash logs.

Sieb_DB_Connect_Avail rule

The Sieb_DB_Connect_Avail (connection availability) rule determines when the Siebel Server is unable to connect to the Siebel Database.

SiebelServer_SiebelServerHealth

Views that render data that this rule is based on:

Table 28. Sieb_DB_Connect_Avail rule definition
Condition	State	Action
#DatabaseAvailability# != 100	Critical	Log message, email Siebel administrator

Interpreting the rule

The Sieb_DB_Connect_Avail:CRITICAL alert indicates that the Siebel server is unable to login to the Siebel database. To verify the server’s ability to connect to the database as the Siebel administrator, use a database utility located on the Siebel server such as SQL*Plus or ISQL to connect to the database. Contact the Siebel Database administrator to diagnose any connectivity issues. You should also verify that the Siebel administrator user id being used by the SiebelServer Agent is still assigned the Siebel administrator responsibility inside the Siebel application.

•

Sieb_Srvr_Availability_Overview graph view .

Sieb_GW_Connect_Avail rule

The Sieb_GW_Connect_Avail (Gateway Server connection availability) rule determines when the Siebel Server is unable to connect to the Gateway Server.

SiebelServer_SiebelServerHealth