Bookshelf Home | Contents | Index | PDF |
Siebel System Monitoring and Diagnostics Guide > Configuring Siebel Server and Component Logging > Configuring Siebel Server Component Logging > Examples of Component Log FilesThis 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 FileThe 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 23. 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 2015-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 Example of Server Request Broker Log FileThe 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 GenericLog GenericInfo 3 0 2015-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 25 and Table 26, 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 SubtypeTable 25 describes the output for a Statement event subtype for the following entry: SQLParseAndExecute Statement 4 0 2015-05-13 14:07:38 select ROW_ID, NEXT_SESSION, MODIFICATION_NUM from dbo.S_SSA_ID Prepare + Execute Event SubtypeTable 26 describes the output for a Prepare + Execute event subtype for the following entry: SQLParseAndExecute Prepare + Execute 4 0 2015-05-13 14:07:38 Time: 0s, Rows: 0, Avg. Time: 0s Example of a Log File for a Server Request ProcessorThe 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 2021 2015-05-11 11:54:24 2015-05-11 12:50:55 +0530 000002d4 001 003f 0001 09 TestMTSBound 4194307 332 2976 m:\siebel\log\TestMTSBound_0004_4194307.log 15.0 [23048] ENU Example of Component Error Log FileThis example displays an error entry from a sample Assignment Manager component log file. The log file is located in the GenericLog GenericError 1 0 2015-05-03 01:02:12 [MERANT][ODBC Oracle 8 driver][Oracle 8]ORA-12541: TNS:no listener
Example of a Detailed Component Log FileThe 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 2015-05-16 23:28:38 0000-00-00 00:00:00 -0600 00000000 001 003f 0001 09 SiebSrvr 0 5956 3856 D:\siebel\15.0\ses\siebsrvr\log\siebel.sdc78275svqe.log 15.0 [23048] ENU ServerLog ServerStartup 1 0000622e49ba14c8:0 2015-05-16 23:28:38 Siebel Enterprise Applications Server is starting up ServerLog LstnObjCreate 1 000062d549ba14c8:0 2015-05-16 23:28:38 Created port 49156 for Workflow Process Batch Manager ServerLog LstnObjCreate 1 000062d549ba14c8:0 2015-05-16 23:28:38 Created port 49157 for Workflow Recovery Manager ServerLog LstnObjCreate 1 000062d649ba14c8:0 2015-05-16 23:28:38 Created port 49158 for Workflow Process Manager ServerLog LstnObjCreate 1 000062d649ba14c8:0 2015-05-16 23:28:38 Created port 49159 for File System Manager ServerLog LstnObjCreate 1 000062d649ba14c8:0 2015-05-16 23:28:38 Created port 49160 for Server Request Processor ServerLog LstnObjCreate 1 000062d649ba14c8:0 2015-05-16 23:28:38 Created port 49161 for Siebel Administrator Notification Component ServerLog ProcessExit 1 0000651d49ba14c8:0 2015-05-16 23:30:03 SmartAnswer 6612 TERMINATED Process 6612 was terminated ServerLog ComponentUpdate 2 000013f949bf1744:0 2015-05-16 23:30:07 CommOutboundMgr INITIALIZED Component has initialized. ServerLog ProcessCreate 1 000013f949bf1744:0 2015-05-16 23:30:15 Created server process (OS pid = 2660 ) for ServerMgr ServerLog ProcessCreate 1 000013f949bf1744:0 2015-05-17 00:45:51 Created server process (OS pid = 7624 ) for ServerMgr ServerLog ProcessCreate 1 000013f949bf1744:0 2015-05-17 03:43:39 Created server process (OS pid = 3236 ) for ServerMgr ServerLog ProcessExit 1 0000651d49ba14c8:0 2015-05-17 03:53:25 ServerMgr 2660 SUCCESS Process 2660 completed Successfully ServerLog ProcessExit 1 0000651d49ba14c8:0 2015-05-17 03:58:35 ServerMgr 3236 SUCCESS Process 3236 completed Successfully ServerLog ProcessCreate 1 000013f949bf1744:0 2015-05-17 03:58:48 Created server process (OS pid = 5816 ) for ServerMgr ServerLog ProcessExit 1 0000651d49ba14c8:0 2015-05-17 03:59:13 ServerMgr 5816 SUCCESS Process 5816 completed Successfully ServerLog ProcessCreate 1 000013f949bf1744:0 2015-05-17 03:59:29 Created server process (OS pid = 5976 ) for ServerMgr ServerLog ProcessExit 1 0000651d49ba14c8:0 2015-05-17 04:34:25 ServerMgr 7624 SUCCESS Process 7624 completed Successfully |
Siebel System Monitoring and Diagnostics Guide | Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |