Bookshelf Home | Contents | Index | Search | PDF |
Siebel Server Administration Guide > Event Logging Administration > Component Event Types >
Component Log File Examples
This section provides examples of component event log files. The event log format and information are detailed and described with the examples.
Component Startup Log File Example
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. See Table 23 for a detailed description of this sample output. 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 2002-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 islocated 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. See Table 22 for this message.
Server Request Broker Log File Example
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). See Table 24 for a detailed description of this sample output. 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 2002-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. See Table 25 and Table 26, respectively, for detailed descriptions of the sample output. 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.
SQLParseAndExecute Statement 4 2002-05-13 14:07:38 select ROW_ID, NEXT_SESSION, MODIFICATION_NUM from dbo.S_SSA_ID
SQLParseAndExecute Prepare + Execute 4 2002-05-13 14:07:38 Time: 0s, Rows: 0, Avg. Time: 0s
Component Error Log File Example
This example displays an error entry from a sample Assignment Manager component log file. The log file is located in the Siebel Server \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). See Table 27 for a detailed description of the sample output. As an error event is of importance, it 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 2002-04-03 01:02:12 [MERANT][ODBC Oracle 8 driver][Oracle 8]ORA-12541: TNS:no listener
Detailed Component Log File Example
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.
ObjMgrSessionInfo ObjMgrLogin 3 2002-02-07 10:54:01 Login name : SADMIN
ObjMgrSessionInfo ObjMgrAuth 3 2002-02-07 10:54:01 Authentication name : SADMIN
DocServerInfo DocServerInfo 0 2002-02-07 10:54:01 Document Server was called.
DocServerInfo DocServerInfo 0 2002-02-07 10:54:01 Document Server input parameters: Service: Document Generator, Method: OnGenerateHTML
CorrespInfo CorrespInfo 0 2002-02-07 10:54:01 Correspondence Service Constructor
CorrespDetail CorrespDetail 2 2002-02-07 10:54:01 Correspondence service method invoked is Start. Correspondence Id is 1-26I5P. From Submit is .
CorrespDetail CorrespDetail 2 2002-02-07 10:54:01 Correspondence service method invoked is OnGenerateHTML. Correspondence Id is 1-26I5P. From Submit is .
CorrespDebug CorrespDebug 3 2002-02-07 10:54:04 Correspondence Service: Verify Recipients...
CorrespDebug CorrespDebug 3 2002-02-07 10:54:04 Correspondence Service: Getting template from filesystem...
CorrespDebug CorrespDebug 3 2002-02-07 10:54:04 Correspondence Service: Attach Word or Word Pro...
CorrespDebug CorrespDebug 3 2002-02-07 10:54:04 Correspondence Service: Generating DataSource...
CorrespDetail CorrespDetail 2 2002-02-07 10:54:04 Number of recipients: 1
CorrespDebug CorrespDebug 3 2002-02-07 10:54:06 Correspondence Service: Performing MailMerge...
CorrespDebug CorrespDebug 3 2002-02-07 10:54:08 Correspondence Service: MailMerge is finished successfully.
CorrespDebug CorrespDebug 3 2002-02-07 10:54:10 Correspondence Service: Shutting down word processor...
DocServerInfo DocServerInfo 0 2002-02-07 10:54:10 Document Server finished successfully.
CorrespInfo CorrespInfo 0 2002-02-07 10:54:11 Correspondence Service Destructor
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Server Administration Guide, Version 7.5, Rev. C Published: 18 April 2003 |