Story

How Can Tracing Be Increased for the Siebel Object Manager?

generate a more detailed log file to assist in troubleshooting any Siebel Object Manager (OM) related behaviors. Increasing the event logging will provide information about the individual processes and steps that are part of that task. This information is especially useful when debugging performance, hang, memory leak, or crash behaviors.
 
NOTE: When you increase the Object Manager event logging levels, the log files will grow larger and require more disk space. Additionally, performance will be impacted as more detailed tracing is written to the log files. Therefore, you should monitor the disk space available under the Siebel Server's log directory and only increase the log levels while you are debugging a specific behavior or as instructed by Siebel Technical Support. You should reset the log levels to their default values when running in a production environment.
                      
By default in Siebel 7.x and 8.0, the Siebel component only writes header information and errors to the component log file. Log files are created in the log directory on the Siebel server and are named using the following format:
 
<Component_Alias>_%Task_Id%.log
 
For example:
 
SCCObjMgr_enu_7204.log
 
There are a number of event types available to increase the amount of information logged. This FAQ does not attempt to detail all of them but details the most useful ones and those that have specific relevance to the Siebel Object Manager component. The table below lists the most commonly used ones and their recommended values:
 
Event Type Alias
Siebel Version
Log Level
Event Description 
v7.0.4
v7.0.5
v7.5.2
v7.5.3
V8.x
MessageFlow
X
X
X
X
X
4
Messages exchanged between the OM and Siebel Web Server Extension (SWSE)
ObjMgrSessionInfo
X
X
X
X
N/A
4
View/Applet (pre-Siebel version 7.5) and User Session login, logout and timeout information
 
NOTE: For additional information about this event type, refer to FAQ 1964.
EventContext
N/A
N/A
X
X
X
4
View/Applet Information and User Actions, in other words, NewQuery, ExecuteQuery, Drilldown
 
NOTE: For additional information about this event type, refer to FAQ 1964.
ObjMgrDataObjLog
X
X
X
X
X*
5
Data Manager object tracking, in other words, creation, use, and deletion of Database Connections, SearchSpecs, SortSpecs, Cursors.

* This event is not available in Siebel 8.1 or later.
ObjMgrLog
X
X
X
X
X
5
General OM events: Load license, open SRF, errors, etc.
ObjMgrBusCompLog
X
X
X
X
X
4
Business Component related events: create and delete
ObjMgrBusServiceLog
X
X
X
X
X
4
Business Service events: create, delete, methods invoked, etc.
 
NOTE: For additional information about this event type and how it was used, refer to Alert 941.
MainThread
X
X
X
X
X
4
Task counter, Task creates and exits (in main Multi Threaded Server log)
TaskEvents
X
X
X
X
X
4
Task creation, context, session timeout and close info
SQLParseAndExecute
X
X
X
X
X
4
SQL Prepare, Execute, Bind variables, etc.
ObjMgrSqlLog
X
X
X
X
X
4/5
4 ‑ SQL statements, bind variables, timing information.
 
5 ‑ Search and Sort spec values, Join definitions.
 
NOTE: To avoid potential adverse behaviors from setting this event type, refer to Alert 945.
SQLProfiling
X
X
X
X
X
4
SQL Profiling information. Helps aid in the diagnosis of a poorly performing component.
SQLSummary
X
X
X
X
X
4/5
SQL Prepare, Fetch and Execute times. Provides detail information regarding the execution of a SQL statement.
SQLSlowQuery
X
X
X
X
X
4
SQL Performance – lists 10 slowest performing queries
 
NOTE: This document covers only the important events related to the Siebel Object Manager components.
 
There are other events that can be turned on for other Siebel components like Siebel Workflow, Siebel EAI, etc. For more information about these events, refer to Siebel Bookshelf version 7.5.3 > Siebel Server Administration Guide > Event Logging Administration > Events and Event Logging.
 
From Siebel versions 7.0.5 and 7.5.3 onwards, it is possible to see the SQL generated by the Siebel Object Manager to be sent to the Fulcrum Search Engine by setting the Generic Log event parameter. This can be set either using the srvrmgr command line or the Server Administration screens. Refer to the following section, Steps to Enable the Component Event, for details on viewing the SQL sent to the Fulcrum Search Engine.
 

Steps To Enable the Component Event

 
Using the Siebel Client (UI)
 
To change the event log level for a component, do the following:
 
  1. In Siebel 7.x release, navigate to Site Map > Server Administration > Components > Component Event Configuration. In Siebel 8.x release, navigate to Site Map > Administration - Server Configuration > Servers > Events.
  2. Highlight the component for which you wish to turn the tracing on.
  3. In the lower applet, select the event type alias and set the log level. For example, to view the SQL sent from the Siebel Search Center to the Fulcrum Search Engine, set the Generic Log event parameter =4.
 
NOTE: There is no need to stop and restart the Siebel Object Manager for the logging to take effect. You only need to start a new session connecting to the Object Manager.
 
Using the Srvrmgr Command Line Utility
 
To change the event log level for a component, type the following:
 
change evtloglvl <event_alias_name=level> for component <component_alias_name>
 
For example, to view the SQL sent from the Siebel Search Center to the Fulcrum Search Engine, type the following:
 
change evtloglvl genericlog=4 for comp <comp_alias_name>
 
You can also use % wildcard to increase logl evel to all parameters at same time
 
        change evtloglvl %=4 for comp <comp_alias_name>
 
If you are using Siebel Call Center in English, the <comp_alias_name> would be SSCObjMgr_enu. For a list of Object Manager components and their aliases, refer to Siebel Bookshelf version 7.7 > Siebel System Administration Guide > Siebel Server Components and Parameters > Siebel Server Components.
 
The log file where this SQL will be generated to is the object manager log file in the Siebel server log directory.
 
An example of the SQL generated in the object manager log file:
 
GenericLog    GenericDetail    4    2003-12-12 12:36:49    Siebel Search:  Executing search.
 
The select statement is
 
SELECT
    ROW_ID, SUMMARY, FILE_NAME, FT_DNAME, REVNUM,VIS_ID,
    TEXT_READER, FT_TEXT_STATUS,TABLENAME(), Relevance(),
    FT_ORIGINAL_SIZE, FULLNAME(),VIS_INFO, DESCRIPTION,
    PRIVATE_FLG, TITLE, VERSION
    FROM "FUL_LIT"
WHERE
    (FUL_LIT.VIS_ID IN  ('0-3P1KT') AND
    (FUL_LIT.SALES_TOOL_TYPE <> 'Component')  AND
    (FUL_LIT.SUMMARY CONTAINS  ~  'null'  OR
    FUL_LIT.EXTERNAL_TEXT CONTAINS  ~  'null' ))
ORDER BY 10 DESC