Bookshelf v8.1/8.2: 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 Table 24. 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, the following information is recorded in the log file.

ServerLog LstnObjInherit 3 0 2003-05-13 11:35:10 Inherited listening object for port 49172

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 Table 23.

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 Table 25. 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 2003-05-13 14:07:31 Set environment variable DB2CODEPAGE=1252

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 Table 26 and Table 27, respectively. 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

Table 26 describes the output for a Statement event subtype for the following entry:

SQLParseAndExecute Statement 4 0 2003-05-13 14:07:38 select ROW_ID, NEXT_SESSION, MODIFICATION_NUM from dbo.S_SSA_ID

Prepare + Execute Event Subtype

Table 27 describes the output for a Prepare + Execute event subtype for the following entry:

SQLParseAndExecute Prepare + Execute 4 0 2003-05-13 14:07:38 Time: 0s, Rows: 0, Avg. Time: 0s

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. Table 28 provides a detailed description of the sample output. This event has a log level of 4.

2021 2009-03-11 11:54:24 2009-03-11 12:50:55 +0530 000002d4 001 003f 0001 09 TestMTSBound 4194307 332 2976 m:\siebel\log\TestMTSBound_0004_4194307.log 8.1.1 [21102] ENU

Table 28. Event Subtype SrmRouting
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: CRLF represents \r\n and is shown as 2 in the log file. LF represents \n and is shown as 1 in the log file. CR represents \r and is shown as 0 in the log file. A custom value is shown as 3 in the log file. 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: True indicates that log files are translated. It is shown as 1 in the log file. False indicates log files are translated. It is shown as 2 in the log file. In this example, 2021 indicates the following: LogEol = 2 (new line character is \r\n) File completion error is 0 File version is 2 LogXlateMsgs = 1 (translate)
2009-03-11 11:54:24	Log file creation timestamp.
2009-03-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, 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 42009-03-16 10:57:02 35928:LOCALTRANS-server] accept() timeout during get conn request If the bit in the: Zero position is set, this least significant bit (LSB) logs the main event type, which in the log file entry is SisnTcpIp. First position is set, the subevent type is logged, which in the log file entry is SisnSockDetail. Second position is set, the event severity is logged, which in the log file entry is 4. Third position is set, the timestamp is logged, which in the log file entry is 42009-03-16 10:57:02. Fourth position is set, the details are logged, which in the log file entry is 35928:LOCALTRANS-server] accept() timeout during get conn request. Fifth position is set, the flow ID and the SARM ID are logged, which in the log file entry is 00000cd049bd8290.
0001	The number of characters in the LogFieldDelim parameter. The default value is \t.
09	Represents the characters in the LogFieldDelim parameter. The default value is \t. For example, 09 represents the character \t, and 09 is the hexadecimal representation of the ASCII value of the character \t.
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.
8.1.1 [21102] 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 Table 29. 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 2003-04-03 01:02:12 [MERANT][ODBC Oracle 8 driver][Oracle 8]ORA-12541: TNS:no listener

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 2009-03-16 23:28:38 0000-00-00 00:00:00 -0600 00000000 001 003f 0001 09 SiebSrvr 0 5956 3856 d:\21112\ses\siebsrvr\log\siebel.sdc78275svqe.log 8.1.1 [21112] ENU

ServerLog ServerStartup 1 0000622e49ba14c8:0 2009-03-16 23:28:38 Siebel Enterprise Applications Server is starting up

ServerLog LstnObjCreate 1 000062d549ba14c8:0 2009-03-16 23:28:38 Created port 49156 for Workflow Process Batch Manager

ServerLog LstnObjCreate 1 000062d549ba14c8:0 2009-03-16 23:28:38 Created port 49157 for Workflow Recovery Manager

ServerLog LstnObjCreate 1 000062d649ba14c8:0 2009-03-16 23:28:38 Created port 49158 for Workflow Process Manager

ServerLog LstnObjCreate 1 000062d649ba14c8:0 2009-03-16 23:28:38 Created port 49159 for File System Manager

ServerLog LstnObjCreate 1 000062d649ba14c8:0 2009-03-16 23:28:38 Created port 49160 for Server Request Processor

ServerLog LstnObjCreate 1 000062d649ba14c8:0 2009-03-16 23:28:38 Created port 49161 for Siebel Administrator Notification Component

ServerLog ProcessExit 1 0000651d49ba14c8:0 2009-03-16 23:30:03 SmartAnswer 6612 TERMINATED Process 6612 was terminated

ServerLog ComponentUpdate 2 000013f949bf1744:0 2009-03-16 23:30:07 CommOutboundMgr INITIALIZED Component has initialized.

ServerLog ProcessCreate 1 000013f949bf1744:0 2009-03-16 23:30:15 Created server process (OS pid = 2660 ) for ServerMgr

ServerLog ProcessCreate 1 000013f949bf1744:0 2009-03-17 00:45:51 Created server process (OS pid = 7624 ) for ServerMgr

ServerLog ProcessCreate 1 000013f949bf1744:0 2009-03-17 03:43:39 Created server process (OS pid = 3236 ) for ServerMgr

ServerLog ProcessExit 1 0000651d49ba14c8:0 2009-03-17 03:53:25 ServerMgr 2660 SUCCESS Process 2660 completed Successfully

ServerLog ProcessExit 1 0000651d49ba14c8:0 2009-03-17 03:58:35 ServerMgr 3236 SUCCESS Process 3236 completed Successfully

ServerLog ProcessCreate 1 000013f949bf1744:0 2009-03-17 03:58:48 Created server process (OS pid = 5816 ) for ServerMgr

ServerLog ProcessExit 1 0000651d49ba14c8:0 2009-03-17 03:59:13 ServerMgr 5816 SUCCESS Process 5816 completed Successfully

ServerLog ProcessCreate 1 000013f949bf1744:0 2009-03-17 03:59:29 Created server process (OS pid = 5976 ) for ServerMgr

ServerLog ProcessExit 1 0000651d49ba14c8:0 2009-03-17 04:34:25 ServerMgr 7624 SUCCESS Process 7624 completed Successfully

Siebel System Monitoring and Diagnostics Guide		Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.