4Configuring Siebel Server and Component Logging
Configuring Siebel Server and Component Logging
This chapter provides descriptions and examples of configuring Siebel Server and component logging using Siebel events. It includes the following topics:
About Configuring Siebel Server and Component Logging
Configuring Siebel Server and component logging captures the internal activity and behavior of Siebel CRM during operation. Siebel Server and component logging use event logging to collect data and write the information to a text log file. You can configure event logging to use system alerts, or you can use event logging with third-party system management applications to notify administrators of any significant or adverse conditions. For information about configuring server components to use system alerts, see Siebel System Administration Guide. You can monitor and manage most Siebel CRM products and functional areas with event logging.
The information collected by event logging can range from error messages to detailed diagnostic logs. Some of the application conditions and operations that result in data written to the log file include:
Catastrophic or error conditions
Change of status of a Siebel Server or server component
Start or finish of a Siebel process or workflow
Specific point in a Siebel process or workflow
When measurable threshold values are reached or exceeded
When operational conditions are met
About Events and Event Logging
The elements of event logging are defined in the following bullets:
Event. An event is created each time you execute a program code (such as running a task).
Event Type. Event types are categories of events.
For information about event types pertinent to a specific part of Siebel CRM, see product-specific documentation or details available on Siebel Bookshelf.
For generic event types used in server component and Siebel Application Object Manager diagnostics, see Common Event Types for Component Diagnostics and Common Event Types for Siebel Application Object Manager Diagnostics.
Event Subtype. Event subtypes are code references that define the event.
Log Level. The log level determines the amount of information that is written to the log file. Log levels are set for event types. The following table lists the log levels of event types.
Severity. A severity level is associated with each event subtype. The severity level and log level share the same scale and are compared when writing events to the log file. The following table lists the severity of event subtypes.
| Log and Severity Level | Description |
|---|---|
0 |
Fatal |
1 |
Errors |
2 |
Warnings |
3 |
Informational |
4 |
Details |
5 |
Diagnostic |
When an event occurs, the severity level of the event (as defined by the event subtype) is compared with the log level of the event type. If the numerical value of the event severity level is equal to or lower than the numerical value of the event type log level, then the event is written to the log file. If the numerical value of the event severity level is higher than the numerical value of the event type log level, then the event is ignored.
For example, the Siebel Server components in the Enterprise Application Integration component group (alias EAI) have an event type called EAI Siebel Wizard. Several event subtypes belong to the EAI Siebel Wizard event type, including:
EAI Siebel Wizard Invalid Business Component with a severity level of 2
EAI Siebel Wizard Invalid MVG with a severity level of 2
EAI Siebel Wizard MVG with a severity level of 3
While the EAI component group is running, the process encounters a multi-value group (MVG). This encounter creates an event of the EAI Siebel Wizard MVG subtype. If the MVG is invalid, then a second event of the EAI Siebel Wizard Invalid MVG subtype is created. If the log level of the EAI Siebel Wizard event type is set to 1, then both events are ignored. If the log level is set to 3, then both events are written to the log file.
Events are logged at the Siebel Server level and the component level. For details on Siebel Server events, see Configuring Siebel Server Logging. For information about component events, see Configuring Siebel Server Component Logging.
About Event Attributes and Log File Format
Each event within the log file contains information about the associated application condition, including:
Event Identifier
Type (category)
Subtype
Timestamp
- Severity Level
- Details (metrics) about the event
For examples of individual events and their attribute values, see Examples of Siebel Server Log Files and Examples of Component Log Files. For an example of a group of events collected within a log file, see Example of a Detailed Component Log File.
Events are written to and collected in a log file in the order of their occurrence. Each log file contains a header that provides information on the individual log file. The following is an example of a log file header:
2021 2017-05-07 21:02:06 0000-00-00 00:00:00 -0800 00000000 001 003f 0001 09 SiebSrvr 2049 1364 1548 C:\siebel\ses\siebsrvr\log\siebel17.server1.log 17.0 [xxxxx] ENU
The following table provides descriptions of the example log file header details.
| Log File Header Detail | Description |
|---|---|
 |
Byte Order Marker (BOM). The BOM is a Unicode format instruction. If the log file header opens with characters like those shown here, then it indicates that the text editor used to view the log file cannot interpret the Unicode instruction. |
2017-05-07 21:02:06 |
Timestamp of log file creation. |
-0800 |
Offset of the local time from the GMT in the format ±HHMM. |
SiebSrvr |
The Siebel Server or component alias to which this log file refers. |
2049 |
Task ID. |
1364 |
OS Process ID (PID). |
1548 |
Thread ID. |
C:\siebel\ses\siebsrv r\log\siebel17.server 1.log |
Log filename. |
17.0 |
Version number. |
[xxxxx] |
Build number. |
ENU |
Language code. |
About Siebel Server Log Files
Siebel Server log files record data for each individual Siebel Server deployed as part of a Siebel Enterprise Server. The Siebel application stores Siebel Server log files in the log directory for each individual Siebel Server as shown in the following table.
| Operating System | Log Directory |
|---|---|
Windows |
|
UNIX |
|
Server log files use the following name convention: EnterpriseServerName.SiebelServerName.log.
Information contained in the Siebel Server log file can be used to determine where to search and investigate component log files for more information. The task ID, which makes up a part of the component log filename, is referenced in messages written to the Siebel Server log file. Locate the appropriate component task ID in the Siebel Server log file and open the task-specific component log that has the task ID in the log filename. For an example of this relationship, see Example of Component Startup Log File.
For more information and examples of Siebel Server log files, see Viewing Siebel Server Log Files and Examples of Siebel Server Log Files.
About Component Log Files
Siebel Server component log files record data for each individual component and task functioning on a particular Siebel Server. These component log files are stored in the Siebel Server log directory on the Siebel Server in which the components are active as shown in the following table. Using event logging with individual components allows you to isolate portions of a Siebel application.
| Operating System | Log Directory |
|---|---|
Windows |
|
UNIX |
|
Component log files use the following naming convention:
ComponentAliasName_SISProcID_TaskID.log
where:
ComponentAliasName is the name of the component running the task.
SISProcID is an internal four-character, zero-padded process ID that is rotating and incremented as component processes are spawned. The minimum numeric value allowed for SISProcID is 1. The maximum value allowed is 2047.
TaskID is a 32-bit internal zero-padded task ID number. Internally, the task ID contains a SISProcID as well as a counter maintained in each component process.
There is one process ID counter for all processes, not for each component. Therefore, you can sort the log files of a particular component by the specific component process.
Individual component task log files can also be consolidated into a single log file by setting the Use Shared Log File (alias LogUseSharedFile) component parameter. For more information about this parameter and on administering the Siebel Server and server component parameters, see Siebel System Administration Guide. For more information about and examples of component log files, see Viewing Component Log Files and Examples of Component Log Files.
Configuring Siebel Server Logging
Siebel Server logging use event types that relate to Siebel Servers. For example, the Server State event type is a Siebel Server-level event that logs changes to the state of the Siebel Server. This topic describes how to configure and view Siebel Server event types. For details, see:
Setting Log Levels for Siebel Server Event Types
This topic describes setting log levels for Siebel Server event types using the Server Manager GUI or Server Manager command-line interface program (srvrmgr). For background information about event logging and event types, see About Configuring Siebel Server and Component Logging. To see the resultant Siebel Server log files, see Viewing Siebel Server Log Files. For examples of Siebel Server log files, see Examples of Siebel Server Log Files.
To set log levels for a Siebel Server event type on Server Manager GUI
Navigate to the Administration - Server Configuration, then Servers view.
In the Siebel Servers list, select the Siebel Server of interest.
From the view tabs, click Events.
In the Event Type list, select the Siebel Server Event Type of interest.
For information about event types pertinent to a specific part of Siebel CRM, see product-specific documentation or details available on Siebel Bookshelf.
In the Log Level field, choose the log level that you want to set for this event type.
For a list of log levels, see the table in About Events and Event Logging.
Click the menu button and then Save Record.
To set log levels for a Siebel Server event type on srvrmgr
Enter:
change evtloglvl event_alias_name=level for server siebel_server_name
Enter:
list evtloglvl for server siebel_server_name
For details on starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.
Viewing Siebel Server Log Files
Siebel Server-level events are written to the Siebel Server log file. The log directory location on Windows is SIEBSRVR_ROOT\log. The log directory location on UNIX is SIEBSRVR_ROOT/enterprises/EnterpriseServerName/SiebelServerName/log.
For background information about event logging and event types, see About Configuring Siebel Server and Component Logging. For more information and file naming conventions, see About Siebel Server Log Files. For examples of Siebel Server log files, see Examples of Siebel Server Log Files.
You can also view Siebel Server event logs from the Server Manager GUI. For information about this task, see Monitoring Siebel Server Log Files.
To assist in analyzing Siebel Server event log files, use the Log File Analyzer (LFA) utility to query and isolate log files of interest. For information about this feature, see Querying System Log Files.
Examples of Siebel Server Log Files
This topic provides examples of Siebel Server event log files. The event log format and information are detailed and described with the examples.
Example of Siebel Server Startup Log File
The following log file samples display what is written to the server log file during a regular startup of a Siebel Server. In this example, events are created that are defined by the event subtypes LstnObjCreate, ProcessCreate, and Startup, all of which have a severity of 1. For a detailed description of the sample output, see the following tables. These events belong to the event type Server Logging (alias ServerLog). If this event type is set to a log level between 1 and 5, then the following information is a sample of what is recorded in the log file.
LstnObjCreate Event Subtype
The following table describes the output for a LstnObjCreate event subtype for the following entry:
ServerLog LstnObjCreate 1 0 2017-05-13 11:35:10 Created port 49173 for Server Request Processor
| Log Detail | Description |
|---|---|
ServerLog |
Event Type alias |
LstnObjCreate |
Event Subtype |
1 |
Event Severity |
0 |
SARM ID |
2017-05-13 11:35:10 |
Date and time of log |
Created port 49173 for Server Request Processor |
Log message |
Startup Event Subtype
The following table describes the output of a Startup event subtype for the following entry:
ServerLog Startup 1 0 2017-05-13 11:35:10 Siebel Application Server is ready and awaiting requests
| Log Detail | Description |
|---|---|
ServerLog |
Event Type alias |
Startup |
Event Subtype |
1 |
Event Severity |
0 |
SARM ID |
2017-05-13 11:35:10 |
Date and time of log |
Siebel Application Server is ready and awaiting requests |
Log message |
ProcessCreate Event Subtype
The following table describes the output of a ProcessCreate event subtype for the following entry:
ServerLog ProcessCreate 1 0 2017-05-13 11:35:10 Created multithreaded server process (OS pid = 2756) for File System Manager with task id 4114
| Log Detail | Description |
|---|---|
ServerLog |
Event Type alias |
ProcessCreate |
Event Subtype |
1 |
Event Severity |
0 |
SARM ID |
2017-05-13 11:35:10 |
Date and time of log |
Created multithreaded server process |
Log message |
(OS pid = 2756) |
Operating System Process ID number |
for File System Manager |
Siebel Server Component |
with task id 4114 |
Task ID number referencing the Siebel Server task |
Configuring Siebel Server Component Logging
Component logging uses event types that relate to a specific Siebel Server component. For example, the SQL Tracing event type is a component-level event that traces SQL statements for a particular server component. This topic describes how to configure and view server component event types. For details, see the following topics:
Setting Log Levels for Component Event Types
This topic describes setting log levels for server component event types using the Server Manager GUI or Server Manager command-line interface program (srvrmgr). For background information about event logging and event types, see About Configuring Siebel Server and Component Logging. To see the resultant Siebel Server component log files, see Viewing Component Log Files. For examples of Siebel Server component log files, see Examples of Component Log Files.
Setting Log Levels for Siebel Server Component Event Types Using the Server Manager GUI
Use the following procedure to set log levels for Siebel Server component event types using the Server Manager GUI.
To set log levels for a Siebel Server component event type using the Server Manager GUI
Navigate to the Administration - Server Configuration screen, then the Servers view.
In the Siebel Servers list, select the Siebel Server of interest.
Click the Components view tab.
In the Components list, select the Siebel Server component of interest.
For example, you might select Call Center Object Manager (ENU).
Click the Events subview tab.
Select the Siebel Server component event type of interest.
For information about event types pertinent to a specific part of Siebel CRM, see product-specific documentation or details available on Siebel Bookshelf.
For generic event types used in server component and Siebel Application Object Manager diagnostics, see Common Event Types for Component Diagnostics and Common Event Types for Siebel Application Object Manager Diagnostics.
In the Log Level field, type in the log level you want to set for this event type, and then step off the record to save it.
For a list of log levels and descriptions, see the table in About Events and Event Logging.
Setting Log Levels for Siebel Server Component Event Types Using srvrmgr
Use the following procedures to set log levels for Siebel Server component event types using the Server Manager command-line interface program (srvrmgr).
To configure a component event type using srvrmgr
Enter:
change evtloglvl event_alias_name=level for component component_alias_name
Enter:
change evtloglvl event_alias_name=level for server siebel_server_name component component_alias_name
Enter:
list evtloglvl for component component_alias_name
Make sure the value for the List of users parameter (alias UserList) is empty.
When this parameter lists one or more particular users, then extended logs are created only for those user IDs in the list.
For information about setting log levels for Siebel Server component parameters, see Setting Log Levels for Component Event Types.
Enter:
change evtloglvl event_alias_name=level for component component_alias_name
Detailed log events for all users are written to the log file.
To set server component event log levels for a specific user using srvrmgr
Make sure the value for the List of users parameter (alias UserList) is set to SADMIN.
For information about setting log levels for Siebel Server component parameters, see Setting Log Levels for Component Event Types.
Enter:
change evtloglvl event_alias_name=level for component component_alias_name
Detailed log events for only SADMIN users are written to the log file.
Note: The log level for other users remains the same.
For details on starting, running, and configuring the srvrmgr program, see Siebel System Administration Guide.
Viewing Component Log Files
Component-level events are written to log files for each task based on the component. The log directory location on Windows is SIEBSRVR_ROOT\log. The log directory location on UNIX is SIEBSRVR_ROOT/enterprises/EnterpriseServerName/SiebelServerName/log. Portions of component task log files can be viewed from the Server Manager GUI. For more information, see Monitoring Server Component Task Log Files. Individual component task log files can also be consolidated into a single log file. For more information and file naming conventions, see About Component Log Files.
To assist in analyzing Siebel Server component event log files, use the Log File Analyzer (LFA) utility to query and isolate log files of interest. For information about this feature, see Querying System Log Files.
Examples of Component Log Files
This topic provides excerpts and examples of component event log files. The event log format and information are described with each of the examples.
Example of Component Startup Log File
The following log file sample displays what is written to the individual Siebel Server component log files during a regular startup of components running on a Siebel Server. In the following example, an event is created for the File System Manager component that is defined by the event subtype LstnObjInherit. For a detailed description of this sample output, see the following table. This event has a severity of 3 and events of this subtype belong to the event type ServerLog. If this event type is set to a log level between 1 and 5, then the following information is recorded in the log file.
ServerLog LstnObjInherit 3 0 2017-05-13 11:35:10 Inherited listening object for port 49172
| Log Detail | Description |
|---|---|
ServerLog |
Event Type alias |
LstnObjInherit |
Event Subtype |
3 |
Event Severity |
0 |
SARM ID |
2017-05-13 11:35:10 |
Date and time of log |
Inherited listening object for port 49172 |
Log message |
This sample log file extract is from the component log file named FSMSrvr_4114.log and is located in the log directory of the Siebel Server. The task ID, 4114, which defines this log file title, corresponds to the log message in the appropriate Siebel Server log file. For this message, see the table in Example of Siebel Server Startup Log File.
Example of Server Request Broker Log File
The following examples display log file entries in a sample Server Request Broker log file. The name of this log file is SRBroker_TaskID.log and is found in the Siebel Server log directory. The first sample captures an event defined by the event subtype GenericInfo, which belongs to the component event type General Events (alias GenericLog). For a detailed description of this sample output, see the following table. This event has a severity of 3 and is recorded to the log file if the General Event log level is set between 3 and 5.
GenericLog GenericInfo 3 0 2017-05-13 14:07:31 Set environment variable DB2CODEPAGE=1252
| Log Detail | Description |
|---|---|
GenericLog |
Event Type alias |
GenericInfo |
Event Subtype |
3 |
Event Severity |
0 |
SARM ID |
2017-05-13 14:07:31 |
Date and time of log |
Set environment variable DB2CODEPAGE=1252 |
Log message |
The next two samples belong to the component event type SQL Parse and Execute. Events were recorded of the event subtype Statement and Prepare + Execute. For detailed descriptions of the sample output, see the following tables. Both of these event subtypes have a severity of 4 and are recorded to the log file if the SQL Parse and Execute event type is set to either 4 or 5.
Statement Event Subtype
The following table describes the output for a Statement event subtype for the following entry:
SQLParseAndExecute Statement 4 0 2017-05-13 14:07:38 select ROW_ID, NEXT_SESSION, MODIFICATION_NUM from dbo.S_SSA_ID
| Log Detail | Description |
|---|---|
SQLParseAndExecute |
Event Type alias |
Statement |
Event Subtype |
4 |
Event Severity |
0 |
SARM ID |
2017-05-13 14:07:38 |
Date and time of log |
select ROW_ID, NEXT_SESSION, MODIFICATION_NUM from dbo.S_SSA_ID |
SQL statement |
Prepare + Execute Event Subtype
The following describes the output for a Prepare + Execute event subtype for the following entry:
SQLParseAndExecute Prepare + Execute 4 0 2017-05-13 14:07:38 Time: 0s, Rows: 0, Avg. Time: 0s
| Log Detail | Description |
|---|---|
SQLParseAndExecute |
Event Type alias |
Prepare + Execute |
Event Subtype |
4 |
Event Severity |
0 |
SARM ID |
2017-05-13 14:07:38 |
Date and time of log |
Time: 0s, Rows: 0, Avg. Time: 0s |
SQL Execution statistics |
Example of a Log File for a Server Request Processor
The following code displays a log file entry in a sample server request processor log file, which can help you troubleshoot why a component request might not run. The name of this log file is SRProc_TaskID.log and is found in the SIEBELSRVR_ROOT\log directory. This code captures an event defined by the event SRMRouting subtype, which belongs to the SRMRouting component event type. The following table provides a detailed description of the sample output. This event has a log level of 4.
2021 2017-05-11 11:54:24 2017-05-11 12:50:55 +0530 000002d4 001 003f 0001 09 TestMTSBound 4194307 332 2976 m:\siebel\log\TestMTSBound_0004_4194307.log 17.0 [xxxxx] ENU
| Log Header Detail | Description |
|---|---|
2021 |
Indicates the values of the LogEol and LogXlateMsgs parameters, as well as the file version and file completion indicators. The first number represents the LogEol parameter. This parameter can take values CRLF, LF, CR, or a custom value where:
The second number represents the file completion indicator as zero and does not change. The third number represents the file version indicator as 2 and does not change. The fourth number represents the value of the LogXlateMsgs (translate log file) parameter in the log file. The LogXlateMsgs parameter can take the values true or false where:
In this example, 2021 indicates the following:
|
2017-05-11 11:54:24 |
Log file creation timestamp. |
2017-05-11 12:50:55 |
Log file completion timestamp. |
+0530 |
Indicates the time difference of the Siebel Server time zone from GMT in the format ±HHMM, where HH represents hours, and MM represents minutes. |
000002d4 |
The number of lines in the log file in hexadecimal format. |
001 |
The segment number in decimal format. |
003f |
The LogEntryFlgs parameter value is applicable only if the LogEntryFmt parameter is set to delimited. If the LogEntryFmt parameter is set to fixed, then all the fields are logged. When the LogEntryFmt is set to delimited, the LogEntryFlgs parameter takes values in decimal format and then internally converts the values to binary format. For example, if the LogEntryFlgs parameter is set to the value of 63, then the value is converted to its binary equivalent of 00111111, and is then processed further. The bits are numbered from right to left, starting from 0 to 7 (the seventh bit is 0, and the zero-position bit is 1). Given the following log file entry: SisnTcpIp SisnSockDetail 4 00000cd049bd8290:0 42017- 05-16 10:57:02 35928:LOCALTRANS-server] accept() timeout during get conn request If the bit in the:
|
0001 |
The number of characters in the LogFieldDelim parameter. The default value is |
09 |
Represents the characters in the LogFieldDelim parameter. The default value is |
TestMTSBound |
The name of the component. |
4194307 |
The task ID. |
332 |
The process ID of the component process. |
2976 |
The thread ID. |
m:\siebel\log\TestMTSBound_0004_4194307.log |
The log file name. |
17.0 [xxxxx] ENU |
The product version, including the language code. |
Example of Component Error Log File
This example displays an error entry from a sample Assignment Manager component log file. The log file is located in the SIEBSRVR_ROOT\log directory and is named AsgnSrvr_TaskID.log. The log message details an event defined by the event subtype GenericError, which belongs to the component event type General Events (alias GenericLog). For a detailed description of the sample output, see the following table. An error event has a severity of 1 and is recorded to the log file if the General Event log level is set between 1 and 5.
GenericLog GenericError 1 0 2017-05-03 01:02:12 [MERANT][ODBC Oracle 8 driver][Oracle 8]ORA-12541: TNS:no listener
| Log Detail | Description |
|---|---|
GenericLog |
Event Type alias |
GenericError |
Event Subtype |
1 |
Event Severity |
0 |
SARM ID |
2017-05-03 01:02:12 |
Date and time of log |
MERANT][ODBC Oracle 8 driver][Oracle 8]ORA-12541: TNS:no listener |
Error message |
Example of a Detailed Component Log File
The previous log file examples are sample extracts from various component log files. As a final example, the following collection of log file messages display the output recorded to a log file after a successful task run by the Document Server component. This log file information is recorded when the appropriate event type log levels are set.
2021 2017-05-16 23:28:38 0000-00-00 00:00:00 -0600 00000000 001 003f 0001 09 SiebSrvr 0
5956 3856 D:\siebel\ses\siebsrvr\log\siebel.sdc78275svqe.log 17.0 [xxxxx] ENU
ServerLog ServerStartup 1 0000622e49ba14c8:0 2017-05-16 23:28:38 Siebel Enterprise
Applications Server is starting up
ServerLog LstnObjCreate 1 000062d549ba14c8:0 2017-05-16 23:28:38 Created port 49156 for
Workflow Process Batch Manager
ServerLog LstnObjCreate 1 000062d549ba14c8:0 2017-05-16 23:28:38 Created port 49157 for
Workflow Recovery Manager
ServerLog LstnObjCreate 1 000062d649ba14c8:0 2017-05-16 23:28:38 Created port 49158 for
Workflow Process Manager
ServerLog LstnObjCreate 1 000062d649ba14c8:0 2017-05-16 23:28:38 Created port 49159 for File
System Manager
ServerLog LstnObjCreate 1 000062d649ba14c8:0 2017-05-16 23:28:38 Created port 49160 for
Server Request Processor
ServerLog LstnObjCreate 1 000062d649ba14c8:0 2017-05-16 23:28:38 Created port 49161 for
Siebel Administrator Notification Component
...
ServerLog ProcessExit 1 0000651d49ba14c8:0 2017-05-16 23:30:03 SmartAnswer 6612 TERMINATED
Process 6612 was terminated
ServerLog ComponentUpdate 2 000013f949bf1744:0 2017-05-16 23:30:07 CommOutboundMgr
INITIALIZED Component has initialized.
ServerLog ProcessCreate 1 000013f949bf1744:0 2017-05-16 23:30:15 Created server process (OS
pid = 2660 ) for ServerMgr
ServerLog ProcessCreate 1 000013f949bf1744:0 2017-05-17 00:45:51 Created server process (OS
pid = 7624 ) for ServerMgr
ServerLog ProcessCreate 1 000013f949bf1744:0 2017-05-17 03:43:39 Created server process (OS
pid = 3236 ) for ServerMgr
ServerLog ProcessExit 1 0000651d49ba14c8:0 2017-05-17 03:53:25 ServerMgr 2660 SUCCESS
Process 2660 completed Successfully
ServerLog ProcessExit 1 0000651d49ba14c8:0 2017-05-17 03:58:35 ServerMgr 3236 SUCCESS
Process 3236 completed Successfully
ServerLog ProcessCreate 1 000013f949bf1744:0 2017-05-17 03:58:48 Created server process (OS
pid = 5816 ) for ServerMgr
ServerLog ProcessExit 1 0000651d49ba14c8:0 2017-05-17 03:59:13 ServerMgr 5816 SUCCESS
Process 5816 completed Successfully
ServerLog ProcessCreate 1 000013f949bf1744:0 2017-05-17 03:59:29 Created server process (OS
pid = 5976 ) for ServerMgr
ServerLog ProcessExit 1 0000651d49ba14c8:0 2017-05-17 04:34:25 ServerMgr 7624 SUCCESS
Process 7624 completed Successfully
Common Event Types for Component Diagnostics
Set the event types in the following table to the indicated log levels for general server component diagnostic purposes. The increased log levels either create log files for the server component of interest or increase the amount of logging information contained in the component log files. For a description on how to set log levels for component event types, see Setting Log Levels for Component Event Types.
| Event Type Name | Event Type Alias | Log Level Setting |
|---|---|---|
Component Tracing |
Trace |
4 |
General Events |
GenericLog |
4 |
Task Configuration |
TaskConfig |
4 |
SQL Tracing |
SQL |
4 |
SQL Error |
SQLError |
4 |
SQL Parse and Execute |
SQLParseAndExecute |
4 |
Common Event Types for Siebel Application Object Manager Diagnostics
Set the event types in the following table to the indicated log levels for general Siebel Application Object Manager diagnostic purposes. The increased log levels either create log files for the Application Object Manager of interest or increase the amount of logging information contained in the Application Object Manager component log files. Increasing the event logging provides information about the individual processes and steps that are part of the Application Object Manager task.
For a description on how to set log levels for Application Object Manager component event types, see Setting Log Levels for Component Event Types.
| Event Type Name | Event Type Alias | Log Level Setting | Description |
|---|---|---|---|
Event to track the flow of a message |
MessageFlow |
4 |
Captures messages exchanged between the Siebel Application Object Manager and Siebel Application Interface. |
Object Manager Session Operation and SetErrorMsg Log |
ObjMgrSessionLog |
4 |
Captures user session login, logout, and timeout information. |
5 |
Captures user name and IP address when the session completes. |
||
Event Context |
EventContext |
4 |
Captures applet and method executed, view names, and screen names that the user navigates to. |
General Object Manager Log |
ObjMgrMiscLog |
5 |
Captures general Application Object Manager events: load license, errors, and so on. |
Object Manager Business Component Operation and SetErrorMsg Log |
ObjMgrBusCompLog |
4 |
Captures business component-related events: create and delete. |
Object Manager Business Service Log |
ObjMgrBusServiceLog |
4 |
Captures business service-related events: create, delete, methods invoked, and so on. |
Main Thread Events |
MainThread |
4 |
Captures task counter, task creates, and task exits (in main Multithreaded Server log). |
Task Related Events |
TaskEvents |
4 |
Captures task creation, context, session timeout, and close info. |
SQL Parse and Execute |
SQLParseAndExecute |
4 |
Captures the SQL insert, update, and delete statements processed by the database connector. It includes the SQL statement and bind variables. The content is similar to the ObjMgrSqlLog event; however, the select statement is not captured by the SQLParseAndExecute event. |
Object Manager SQL Log |
ObjMgrSqlLog |
4 |
Captures the SQL select, insert, update, and delete statements processed by the Application Object Manager data object layer. Includes the SQL statement and bind variables. It also captures the preparation, execute, and fetch time for the SQL cursor. |
5 |
Captures internal and customer-defined search and sort specifications, the joins processed for queries, as well as a call stack of the operation performed. Setting this event to log level 5 incurs a significant performance impact because a callstack is generated. Only set this event to log level 5 in consultation with Oracle Global Customer Support. |
||
SQL Summary |
SQLSummary |
4 |
Captures SQL prepare, fetch, and execute times. Provides detailed information regarding the execution of an SQL statement. |
Security Adapter Log |
SecAdptLog |
5 |
Captures security adapter tracing information to the Application Object Manager log file. |
Security Manager Log |
SecMgrLog |
5 |
Captures security manager tracing information to the Application Object Manager log file. |