Siebel System Monitoring and Diagnostics Guide > Monitoring Siebel Server Run-Time Operations > Analyzing System Data with Siebel Run-Time Data >

Identifying Task Log Files From the Siebel Server Log File

Map the Siebel Server log file to its Siebel Server components and their log files by identifying the task ID in the Siebel Server log file. Review the task log file for further information on the task performance.

NOTE:  The detail of the log file depends on logging levels set for event types for each component. For details on event types and event logging, see Configuring Siebel Server and Component Logging.

For information on analyzing other Siebel application diagnostic data, see Analyzing System Data with Siebel Run-Time Data.

To identify task IDs from Siebel Server log files

1. Access a Siebel Server log file by using the Server Manager GUI. For details on this procedure, see Monitoring Siebel Server Log Files.

   Also access Siebel Server log files by:

   • Using the Log File Analyzer. For details on this procedure, see Querying System Log Files.
   • Opening the log file itself. For details on locations and naming convention of Siebel Server log files, see About Siebel Server Log Files.
2. Review the Text field of each log file entry for the Siebel Server component of interest.
3. The text field of each Siebel Server component log file entry also contains the task ID number started for this component.
4. Access the Siebel Server component task list. For details on this procedure, see Monitoring Server Component Task State.
5. Query the list with the task ID number identified in the Siebel Server log file.
6. Review the status of the Siebel Server component task by reviewing the log file, state value, and statistics for this task. For details on these procedure, see Monitoring Server Component Task Status.

NOTE:  The task ID number identified in step 3 can also be used to find the individual task log file stored in the log folder. The name of the task log file contains the task ID for the component. For example, in SCCObjMgr_enu_19369.log, the task ID is 19369.