Tracing Activities and Events for Siebel Object Manager

With a lot of things going on for the Siebel Object Manager, it may become necessary to track activities and events on it for the purposes of troubleshooting or performance monitoring.  To track useful information, we need to increase logging level to generate more detailed log files, which will help us 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.

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, it is critical for Siebel administrators to monitor the disk space available under the Siebel Server's log directory during the tracking process.  You should only increase the log levels while you are debugging a specific behavior, and reset the log levels to their default values immediately after the tracking process.  Extra caution is needed when you increase logging level in a production environment.
                     
Oracle Support specified a number of event types available to increase the amount of information logged. The following table 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

For example, if we want to track SQL statements generated by certain activities and events, we can increase logging level as:

change evtloglvl ObjMgrSqlLog=4,sqlparseandexecute=4 for comp SCCObjMgr_enu 

Run activities for tracking.

Reset level:

change evtloglvl ObjMgrSqlLog=1,sqlparseandexecute=1 for comp SCCObjMgr_enu 

Get log file, for example, SCCObjMgr_enu_0009_9437203.log, and check SQL statement.  You should be able to find the SQL statement, parameters, and execution information in the log file.

Reference

Oracle (2013). How Can Tracing Be Increased for the Siebel Object Manager? (Doc ID 477897.1).