6Querying System Log Files

Querying System Log Files

Querying log files produced by a Siebel application is a useful diagnostic task to resolve problems that occur during any stage of operation. The Log File Analyzer (LFA) is a command-line utility that assists with this analysis. It includes the following topics:

• About the Log File Analyzer

• Strategy for Analyzing Log Files

• Process for Analyzing Log Files with LFA

• Configuring the Log File Analyzer

• Starting the Log File Analyzer

• About Running Log File Analyzer Commands

• Creating and Saving LFA Queries

• Filtering LFA Queries

• Saving Log File Analyzer Output to Text Files

• Displaying Saved Query Output

• Interrupting Log File Analyzer Queries

• Listing Query Command Key Words

• Listing Log Event Fields Display Status

• Showing Log Event Fields in LFA Results

• Hiding Log Event Fields in LFA Results

• Deleting Log File Analyzer Saved Query Results

• Listing Log File Analyzer Queries and Run-time Details

• Listing Log File Information Using Log File Analyzer

• Exiting Log File Analyzer

• Troubleshooting Log File Analyzer Errors

About the Log File Analyzer

The Siebel Log File Analyzer (LFA) is a command-line utility designed to search through Siebel log files and isolate information of interest. Use the LFA to analyze and review the content of log files and to compile analysis information from these files.

Run the LFA to query log files across Siebel Servers and Siebel Application Interface while filtering on one or more of the following items:

• User name

• Log levels

• Literal values

• Events or subevents

• Session IDs

• Time and date of log files

• Component

The LFA creates analysis output, which can be reviewed from the command-line or saved to text files.

For details on the process to run the LFA, see Process for Analyzing Log Files with LFA.

LFA Language Considerations

The LFA uses information in the events of the main Siebel Server log file to determine what components are available. The events in this log file are translated for different languages. To understand the format of the events for different languages, the LFA reads information in the language files located in the locale subdirectory of the Siebel Server root directory (for example, /siebel/siebsrvr/locale).

If the language files are changed, then the LFA might not be able to recognize certain key events in the main Siebel Server log file, which lead to run-time errors.

Strategy for Analyzing Log Files

The strategy for analyzing log files depends on the type of issues encountered. Identify whether the issue of interest is related to a particular user or the application system in general. Run the Log File Analyzer (LFA) using the strategy applicable to the identified issue.

• For a strategy to use the LFA to examine user issues, see Analyzing User Issues

  .

• For a strategy to use the LFA to examine system issues, see Analyzing System Issues

  .

For information and details on the process of using the LFA, see Process for Analyzing Log Files with LFA.

Analyzing User Issues

For user issues that are not immediately resolvable, log files provide additional information logged by the application regarding a user’s time spent accessing and using the application.

The LFA gives the administrator the capability of querying across numerous log files for log events that were pertinent to the user's session. For example, in a situation where a user named Casey Smith reports an issue with her application at approximately 13:00, use the LFA to query events pertinent to Casey that occurred between 12:30 and 14:00. To refine the results, include the condition that the log level must be greater than or equal to one, which represents an error condition.

The LFA output includes information as to which file each log event came from. The administrator can, after finding an error or other log event of interest, check back in the original log file and look for events nearby that might give additional context useful for troubleshooting the issue.

Note: To query log files for users, make sure the environment variable SIEBEL_LOG_EVENTS is set to 4. For more information about environment variables, see Common Event Types for Component Diagnostics.

Analyzing System Issues

For general system issues not involving user issues (for example, a problem with a workflow), the LFA assists the administrator in isolating and resolving issues relating to general system usage.

For example, if the workflow processor is known to have failed within a particular time frame, then use the LFA to search for log events that occurred during that time frame, and then look at the log files in which the events are contained for more specific detail.

As a preventative measure, the LFA is also useful to periodically check log files for any errors, even if no system issue is apparent at that time.

Process for Analyzing Log Files with LFA

To analyze log files with the Log File Analyzer (LFA), perform the following tasks:

1. Configure the LFA to access the appropriate Siebel Server and Siebel Application Interface log files, if necessary. For more information about this task, see Configuring the Log File Analyzer.

2. Start the LFA. For more information about this task, see Starting the Log File Analyzer.

3. Query the log files using LFA. For information about this task, see Creating and Saving LFA Queries. For general information about running the LFA, see About Running Log File Analyzer Commands.

For strategies on analyzing log files using the LFA, see Strategy for Analyzing Log Files.

Configuring the Log File Analyzer

Configure the Log File Analyzer (LFA) by accessing and editing the LFA configuration file, which has the default name, logreader.cfg. The LFA uses the LFA configuration file when started to reference Siebel Server locations, Siebel Application Interface locations, and other run-time details.

This task is the first step in Process for Analyzing Log Files with LFA. Once the LFA is configured, this step is optional unless further changes are necessary.

The default location for the LFA configuration file is the binary (bin) subdirectory of the Siebel Server root directory (for example, /siebel/siebsrvr/bin).

The LFA configuration file contains sections that configure which log files are analyzed by the utility and what content is reviewed. Edit the appropriate sections in the configuration file with a text editor. For LFA configuration file parameters and their descriptions, see the following table. For an example of a typical configuration file, see Example of a Log File Analyzer Configuration File.

Section	Parameter	Description
[elements]	Siebel Server Identification Tag	Under the [elements] section, list Siebel Servers searchable by the LFA using the following format: Siebel Server Identification Tag = server where Siebel Server Identification Tag is a unique tag name identifying the Siebel Server of interest. This tag can be the Siebel Server name, but can also be any other configurable value, for example: [elements] SiebelServer1=server
	Siebel Application Interface Identification Tag	Under the [elements] section, list Siebel Application Interface instances that are searchable by the LFA using the following format: Siebel Application Interface Identification Tag = plug-in where Siebel Application Interface Identification Tag is a unique tag identifying the Siebel Application Interface of interest. This tag can be the Siebel Application Interface name, but can also be any other configurable value, for example: [elements] SiebelAI1=plugin
[Siebel Server Identification Tag]	Path	Each Siebel Server identification parameter listed in the [elements] section has a respective section of its own with its name in square brackets. The path parameter of each Siebel Server section denotes the location of the associated log files for that Siebel Server. For example: [SiebelServer1] Path = //siebel/ses/siebsrvr/log
[Siebel Server Identification Tag.Siebel Server Component Name]	shortname	List Siebel Server component display names in square brackets to allow the LFA to search for component references in log files specific to a Siebel Server. Add the Siebel Server component alias as the value for the short name parameter. For example: [SiebelServer1.Server Request Broker] shortName=SRBroker For a listing of Siebel Server components and their aliases, see Siebel System Administration Guide.
[Siebel Application Interface Identification Tag]	Path	Each Siebel Application Interface identification parameter listed in the [elements] section has a section of its own with its name in brackets ([ ]). The path parameter of each Siebel Application Interface section denotes the location of the associated log files for that Siebel Application Interface. For example: [SiebelAI1] Path = //siebel/SiebelAI1/log
[Render]	event	Displays information on log events, if enabled. Set to 1 to enable; set to 0 to disable. The parameter information in the [render] section is also controlled by using commands during the running of the LFA. For more information, see About Running Log File Analyzer Commands.
	subevent	Displays information on log subevents, if enabled. Set to 1 to enable; set to 0 to disable.
	loglevel	Displays information on log level of event subtypes. Set to 1 to enable; set to 0 to disable.
	time	Displays log timing information in enabled. Set to 1 to enable; set to 0 to disable.
	file	Displays log file path information, if enabled. Set to 1 to enable; set to 0 to disable.

Note: Do not modify the sections entitled [schemes], [user], and [session].

Example of a Log File Analyzer Configuration File

The following example Log File Analyzer (LFA) configuration file is intended for a Siebel application with two Siebel Servers, named SiebSrv1 and SiebSrv2, and three instances of Siebel Application Interface, named SiebelAI1, SiebelAI2, and SiebelAI3. The LFA configuration file also contains alias information on two Siebel Server components, Server Request Broker and Call Center Object Manager. Using this configuration file, the LFA searches all Siebel Server and Siebel Application Interface log files, has the ability to search on the two Siebel Server components listed, and displays all information except log level and the log file path.

For descriptions of the individual sections and parameters, see Configuring the Log File Analyzer.

[elements]
SiebSrv1=server
SiebSrv2=server
SiebelAI1=plugin
SiebelAI2=plugin
SiebelAI3=plugin

[SiebSrv1]
Path = //siebel/ses/siebsrvr/log

[SiebSrv2]
Path = //siebel/ses/siebsrvr/log

[SiebSrv1.Server Request Broker]
shortName=SRBroker

[SiebSrv2.Call Center Object Manager (ENU)]
shortName=SCCObjMgr

[SiebelAI1]
Path = //siebel/SiebelAI1/log

[SiebelAI2]
Path = //siebel/SiebelAI2/log

[SiebelAI3]
Path = //siebel/SiebelAI3/log

[Render]
event=1
subevent=1
loglevel=0
time=1
file = 0

Starting the Log File Analyzer

Starting the Log File Analyzer (LFA) is the second step in the Process for Analyzing Log Files with LFA. For background information about the LFA, see About the Log File Analyzer.

The LFA utility resides in the binary (bin) subdirectory of Siebel Server root directory under Microsoft Windows as the executable logreader.exe or as binaries under UNIX.

The procedure for starting the LFA under Microsoft Windows is available in Starting the Log File Analyzer Under Microsoft Windows.

The procedure for starting the LFA under UNIX is available in Starting the Log File Analyzer Under UNIX.

Starting the Log File Analyzer Under Microsoft Windows

Use the following command to start the Log File Analyzer (LFA) command-line utility under Microsoft Windows.

To start the Log File Analyzer under Microsoft Windows

1. Navigate to the binary (bin) subdirectory within the Siebel Server root directory (for example, C:\siebel\siebsrvr\bin).

2. Make sure the LFA configuration file (logreader.cfg) is present in the same directory as the utility. If this file is located in another directory, or has another name, then use the /f parameter described in the following table.

   For more information about the configuration file, see Configuring the Log File Analyzer.

3. At the Windows command prompt, enter logreader.exe using, as necessary, parameters listed in the following table.

   The log reader command prompt appears after a successful start as follows:

   logreader>
   

4. Run the LFA by using the commands described in About Running Log File Analyzer Commands.

Note: Make sure the DLL files MSVCR70D.dll and MSVCP70D.dll are present in the LFA directory.

The following table describes the parameters available for use during the starting of the LFA.

Parameter	Description	Example
/h	Lists the parameters available for use with the LFA utility.	logreader /h
/f	Locates the LFA configuration file if it is not present in the LFA utility directory or if the configuration file is named differently than logreader.cfg. Include the path or new configuration filename after the /f parameter. If the configuration filename includes a space, then enclose the argument with quotation marks.	logreader /f abc.cfg or log reader /f g:\abc\abc.cfg
/i	Specifies an input file that contains LFA commands. At startup, the LFA provides output from the commands listed in the input file. Include the filename and path, if necessary, after the /i parameter.	logreader /i g:\abc\abc.txt

Note: Use the /f and /i parameters independently or together.

Starting the Log File Analyzer Under UNIX

Use the following command to start the Log File Analyzer (LFA) command-line utility under UNIX.

To start the Log File Analyzer under UNIX

1. Make sure the LD_LIBRARY_PATH (Oracle Solaris), SHLIB_PATH (HP-UX), or LIBPATH (AIX) environment variable contains the full pathname for your database client library directory. For more information about these variables, see Siebel Installation Guide for UNIX.

2. Make sure the LFA configuration file (logreader.cfg) is present in the same directory as the utility. If this file is located in another directory, or has another name, then use the /f parameter described in the table in Starting the Log File Analyzer Under Microsoft Windows. For more information about the configuration file, see Configuring the Log File Analyzer.

3. Enter logreader using, as necessary, other parameters listed in the table in Starting the Log File Analyzer Under Microsoft Windows.

   The logreader command prompt appears after a successful start as follows:

   logreader>
   

4. Run the LFA by using the commands described in About Running Log File Analyzer Commands.

About Running Log File Analyzer Commands

Running the Log File Analyzer (LFA) allows you to search and filter information contained in Siebel application log files. For overall strategy on running the LFA, see Strategy for Analyzing Log Files.

Make sure when running the LFA that you enter commands and parameters correctly. The following information is common to all LFA commands:

• The LFA is case sensitive.

• Enclose any parameters that contain spaces with quotation marks.

The following topics list instructions for running the LFA:

• Creating and Saving LFA Queries. Creating and executing a query is the fundamental task associated with the LFA.

• Filtering LFA Queries. Filtering queries assists the user to isolate diagnostic information of interest.

  Note: Move log files to a nonproduction environment before querying them with the LFA. As the LFA parses through potentially large and numerous log files, using the LFA in a production environment might reduce overall system performance.

Creating and Saving LFA Queries

Creating and executing a query is the fundamental task associated with the Log File Analyzer (LFA). Creating saved queries is a task in the Process for Analyzing Log Files with LFA.

Run queries using the LFA query command to search log files based on users, literal values, sessions, severity, events, subevents, log times, or combinations of these items.

For descriptions on running these commands, see the following topics.

The LFA saves the results of each query to memory or saves it to a text file. For details on displaying saved queries, see Displaying Saved Query Output. For details on saving output to a text file, see Saving Log File Analyzer Output to Text Files.

To stop a query before it finishes, see Interrupting Log File Analyzer Queries.

Querying Log Files for Users

To query log files for users, you must first set an environment variable log level, and add sections to the logreader.cfg file.

Note: To run queries for a specific user using the option user, you must run the query against the Siebel Application Interface log files.

Use the following procedures to query log files for users.

To prepare for querying events associated with users

1. Make sure the SIEBEL_LOG_EVENTS environment variable is set to 4.

   For more information about setting environment variables, see Setting Log Levels for Component Event Types.

2. Add new sections to the logreader.cfg file by doing the following:

   1. Add a SWE=plugin section under the [elements] section.

   2. Create a new [SWE] section with the following:

      Path = <swe log files directory location>.

Use the following procedure to search log files for events associated with individual users.

To query for events associated with a particular user

• Using the command-line interface, enter:

  query query_name where user = user_name
  

  where:

  • query_name is the query command output stored in memory under this name.

  • user_name is the user of interest in log files.

An example of this query command is as follows:

query asqry where user = asmith

This command queries log files for events associated with user asmith and saves the output to memory under the name asqry.

For other options of the Log File Analyzer (LFA) query command, see Creating and Saving LFA Queries.

Querying Log Files for Literal Values

Use the following procedure to search log files for specific literal values. For other options of the Log File Analyzer (LFA) query command, see Creating and Saving LFA Queries.

To query for a literal value

• Enter:

  query query_name where literal = literal_value
  

  where:

  • query_name is the query command output stored in memory under this name.

  • literal_value is the literal value of interest in log files.

An example of this query command is as follows:

query litqry where literal = Parameter

This command queries log files for events associated with literal Parameter and saves the output to memory under the name litqry.

Querying Log Files for Error Messages

Use the following procedure to search log files for error messages. This command is an application of querying for literal values. For other options of the Log File Analyzer (LFA) query command, see Creating and Saving LFA Queries.

To query for an error message

• Enter:

  query query_name where literal = error_message_number
  

  where:

  • query_name is the query command output stored in memory under this name.

  • error_message_number is the error message number of interest in log files.

An example of this query command is as follows:

query errorqry where literal = SBL-ASG-00001

This command queries log files for events associated with error message number SBL-ASG-00001 and saves the output to memory under the name errorqry.

Querying Log Files for Sessions

Use the following procedure to search log files for specific sessions. For other options of the Log File Analyzer (LFA) query command, see Creating and Saving LFA Queries.

To query for events associated with a particular session

• Enter:

  query query_name where session = session_ID
  

  where:

  • query_name is the query command output stored in memory under this name.

  • session_ID is the session ID of interest in log files.

An example of this query command is as follows:

query sesqry where session = !1.15bc.c425.3f302b17

This command queries log files for events associated with session ID !1.15bc.c425.3f302b17 and saves the output to memory under the name sesqry.

Querying Log Files of a Particular Severity

Use the following procedure to search log files for events of a specific severity. For other options of the Log File Analyzer (LFA) query command, see Creating and Saving LFA Queries.

Events are categorized from 0 to 5, 0 being the most severe or critical. For more information about event severity and event logging, see Siebel System Administration Guide.

This command includes events of the indicated severity as well as events of a greater severity. For example, if you query for a severity of 2, then events of severity 0 and 1 are also included in the output.

To query for events associated with a particular severity

• Enter:

  query query_name where loglevel = severity_value
  

  where:

  • query_name is the query command output stored in memory under this name.

  • severity_value is the severity value of interest (integer value from 0 to 5).

An example of this query command is as follows:

query svtqry where loglevel = 1

This command queries log files for events associated with a severity of 0 and 1 and saves the output to memory under the name svtqry.

Querying Log Files for a Particular Log Event

Use the following procedure to search log files for a specific log event. For other options of the Log File Analyzer (LFA) query command, see Creating and Saving LFA Queries.

For a partial listing of log events and for more information about event logging, see Siebel System Administration Guide.

To query for events associated with a particular log event

• Enter:

  query query_name where event = event_name
  

  where:

  • query_name is the query command output stored in memory under this name.

  • event_name is the log event name of interest.

An example of this query command is as follows:

query evtqry where event = SessMgr

This command queries log files for log events named SessMgr and saves the output to memory under the name evtqry.

Querying Log Files with a Particular Log Subevent

Use the following procedure to search log files for a specific log subevent. For other options of the Log File Analyzer (LFA) query command, see Creating and Saving LFA Queries.

For a partial listing of log subevents and for more information about event logging, see Siebel System Administration Guide.

To query log entries associated with a particular log subevent

• Enter:

  query query_name where subevent = subevent_name
  

  where:

  • query_name is the query command output stored in memory under this name.

  • subevent_name is the log subevent name of interest.

An example of this query command is as follows:

query subevtqry where subevent = SisnNetGeneric

This command queries log files for log subevents named SisnNetGeneric and saves the output to memory under the name subevtqry.

Querying Log Files After a Particular Time

Use the following procedure to search log files created after a specific time. For other options of the Log File Analyzer (LFA) query command, see Creating and Saving LFA Queries.

To query events logged after a certain time

• Enter:

  query query_name where time from "YYYY-MM-DD HH:MM:SS"
  

  where:

  • query_name is the query command output stored in memory under this name.

  • "YYYY-MM-DD HH:MM:SS" is the date and time of interest.

  Note: The exact time portion of the date and time parameter, HH:MM:SS, can be omitted. In this case, the date’s base time defaults to 00:00:00.

An example of this query command is as follows:

query timeqry where time from "2017-05-01 16:30:00"

This command queries log files created after May 1, 2017 at 4:30 PM, and saves the output to memory under the name timeqry.

This command is useful in combination with other parameters to filter results. For more information, see Querying Log Files Using Multiple Conditions.

Querying Log Files Within a Time Interval

Use the following procedure to search log files created within a specific time interval. For other options of the Log File Analyzer (LFA) query command, see Creating and Saving LFA Queries.

To query events logged within a certain time interval

• Enter:

  query query_name where time from "YYYY-MM-DD HH:MM:SS" to "YYYY-MM-DD HH:MM:SS"
  

  where:

  • query_name is the query command output stored in memory under this name.

  • "YYYY-MM-DD HH:MM:SS" is the date and time of interest.

  Note: The exact time portion of the date and time parameter, HH:MM:SS, can be omitted. In this case, the date’s from-time defaults to 00:00:00 and the to-time defaults to 23:59:59.

An example of this query command is as follows:

query timeintqry where time from "2017-05-01 16:30:00" to "2017-05-05"

This command queries log files created between May 1, 2017 at 4:30 PM and May 5, 2017 at 11:59 PM, and saves the output to memory under the name timeintqry.

This command is useful in combination with other parameters to filter results. For more information, see Querying Log Files Using Multiple Conditions.

Querying Log Files for Components

Use the following procedure to search log files for a specific Siebel Server component. For other options of the Log File Analyzer (LFA) query command, see Creating and Saving LFA Queries.

Make sure the LFA configuration file contains information on the Siebel Server component of interest. For more information, see Configuring the Log File Analyzer.

For more information about Siebel Server components, see Siebel System Administration Guide.

To query log entries for a particular Siebel Server component

• Enter:

  query query_name where component = component_name
  

  where:

  • query_name is the query command output stored in memory under this name.

  • component_name is the Siebel Server component name of interest.

Note: The component_name parameter value is either the long form or alias form of the Siebel Server component name. For a list of component names and aliases, see Siebel System Administration Guide.

An example of this query command is as follows:

query compqry where component = SCCObjMgr

This command queries log files for the Call Center Object Manager (alias SCCObjMgr) and saves the output to memory under the name compqry.

Querying Log Files Using Multiple Conditions

This topic provides examples of combination query commands using multiple conditions. For a list of individual query command conditions and their use, see Creating and Saving LFA Queries.

The logical AND and OR operators are also applicable to the Log File Analyzer (LFA) query command. To add clarity to multiple condition commands, group condition sets in parentheses.

• query litasqry where (literal = Parameter) or (user = asmith)

  This command queries log files for the literal Parameter or the user asmith. It saves the output to memory under the name litasqry.

• query aqry where literal = Parameter and literal = SBL-GEN

  This command queries log files for the literal Parameter and the literal SBL-GEN. It saves the output to memory under the name aqry.

• query asaugqry where user = asmith time from 2017-05-05

  This command queries log files for the user asmith after May 05, 2017. It saves the output to memory under the name asaugqry.

• query asaugqry where user = asmith time from "2017-05-05 15:20:00" to "2017-05-05 15:30:00"

  This command queries log files for the user asmith during the ten-minute period between 3:20 PM and 3:30 PM on May 05, 2017. It saves the output to memory under the name asaugqry.

Filtering LFA Queries

Use the show command to further refine the output of saved queries. For information about querying log files and creating saved queries, see Creating and Saving LFA Queries.

For information about displaying a saved query or multiple saved queries, see Displaying Saved Query Output.

To filter saved query information

• Enter:

  show query_name where_clause
  

  where:

  • query_name is the query command output stored in memory under this name.

  • where_clause is the WHERE clause used to filter display results using key words.

For a list of key words available for use with the Log File Analyzer (LFA), see Listing Query Command Key Words. The syntax of where clauses used with the show command are similar to those used with the query commands. Review Creating and Saving LFA Queries for more information.

Use multiple where clause conditions and the logical operators AND and OR to further filter an individual or multiple saved queries. For examples of these types of commands, see Examples of Filtered Saved Queries.

To save filtered output from the show command, save the results to a text file. For description of this task, see Saving Log File Analyzer Output to Text Files. Filtered output from the show command cannot be saved in memory.

Examples of Filtered Saved Queries

The following examples display the type of filtering available on saved queries using the show command.

• show aquery where user = asmith

  This command filters the saved query aquery for information specific to user asmith.

• show aquery where user = asmith and literal = Parameter time from "2017-05-05 15:20:20" to "2017-05-05 15:30:00" > out.dat

  This command filters the saved query aquery for information on user asmith and the literal value parameter between the time of 3:20 and 3:30 PM on May 05, 2017. The command also stores the results of the filtered query to a text file named out.dat.

• show aquery, bquery where user = asmith and literal = Parameter time from "2017-05-05 15:20:20" to "2017-05-05 15:30:00" > out.dat

  This command filters the saved queries aquery and bquery based on the same conditions in the previous bullet.

Saving Log File Analyzer Output to Text Files

Use the following procedure to save the results of a Log File Analyzer (LFA) command to a text file. For information about running the LFA, see About Running Log File Analyzer Commands. Any LFA command that creates output can have the output channeled to a file.

To save Log File Analyzer output to text files

• Enter:

  log_file_analyzer_command > file_name.txt
  

  where:

  • log_file_analyzer_command is the LFA command.

  • file_name.txt is the name of the output text file.

    Make sure to:

  • Include the > character when saving output to a text file.

  • Specify a path name with the text filename if you want to save the log file to another directory, and not the Log File Analyzer (LFA) directory.

Example:

query litqry where literal = Parameter > output1.txt

This command saves the output from the litqry saved query to the text file named output1.txt. The LFA stores this output text file in the same directory as the Log File Analyzer directory.

Displaying Saved Query Output

Use the following procedures to display results of one or more saved query commands to the screen. For a listing of saved queries, see Listing Log File Analyzer Queries and Run-time Details.

For more information about the query command, see Creating and Saving LFA Queries.

The Log File Analyzer (LFA) also saves query command output to text files. For more information about this task, see Saving Log File Analyzer Output to Text Files.

To show saved query output to the screen

• Enter:

  show query_name
  

  In this command, query_name is the query command output stored in memory under this name.

Example:

show evtqry

This example displays the output from a previous query command named evtqry.

Note: The LFA only displays queries saved to memory during a given session.

To show multiple saved query output to the screen

• Enter:

  show query_name_1, query_name_2, ... , query_name_N
  

  In this command, query_name_N is the query command output stored in memory under this name.

Example:

show evtqry1, evtqry2

This example displays the output from two previous query commands named evtqry1 and evtqry2.

Interrupting Log File Analyzer Queries

Use the following procedure to interrupt a query command. For more information about the query command, see Creating and Saving LFA Queries.

To interrupt a query command in operation

• Press CTRL-C during the operation of the command.

Listing Query Command Key Words

Use the following procedure to list the key words available for use with the query command where clause. For detailed descriptions of use for each key word, see Creating and Saving LFA Queries.

To list the query command key words

• Enter:

  keys
  

  The key words are output to the screen.

Listing Log Event Fields Display Status

Use the following procedure to list the display status for log event fields. The value 1 indicates the log event field is set to display. The value 0 indicates the log event field is set to hide.

To list log event fields display status

• Enter:

  fields
  

To change the display status at run-time, see the task Showing Log Event Fields in LFA Results or Hiding Log Event Fields in LFA Results for more information.

Set the default display status of the event log fields by modifying the Log File Analyzer (LFA) configuration file. For more information about the LFA configuration file, see Configuring the Log File Analyzer.

Showing Log Event Fields in LFA Results

Use the following procedures to show log file fields in the output from the Log File Analyzer (LFA) during an individual LFA session. You can also set this information in the LFA configuration file, which is applicable to all LFA sessions. For more information, see Configuring the Log File Analyzer.

To list the current event log field display status, see Listing Log Event Fields Display Status.

To show log file fields in the LFA output

• Enter:

  showfield log_field_name
  

  In this command, log_field_name is the name of the log field name for display.

For a list of the available display fields, see the following table.

Set multiple log file fields to show on a single showfield command by separating each log file field with a space or comma.

Log File Field	Description
event	Name of the event.
subevent	Name of the subevent.
loglevel	Severity of the log file event.
file	File and path name of the log file.
time	Date and time of the log file.

Hiding Log Event Fields in LFA Results

Use the following procedures to hide log file fields in the output from the Log File Analyzer (LFA) during an individual LFA session. You can also set this information in the LFA configuration file, which is applicable to all LFA sessions. For more information, see Configuring the Log File Analyzer.

To list the current event log field display status, see Listing Log Event Fields Display Status.

To hide log file fields in the LFA output

• Enter:

  hidefield log_field_name
  

  In this command, log_field_name is the name of the log field name for display. For a list of the available display fields, see the table in Showing Log Event Fields in LFA Results.

Set multiple log file fields to hide on a single showfield command by separating each log file field with a space or comma.

Deleting Log File Analyzer Saved Query Results

Use the following procedure to delete saved queries. For more information about querying log files, see Creating and Saving LFA Queries.

Note: Deleting saved queries does not delete queries saved as text files.

To delete Log File Analyzer query results

• Enter:

  delete query_name
  

  In this command, query_name is the query command output stored in memory under this name.

Delete multiple saved queries by separating each query name with a space or comma when using the delete command.

Listing Log File Analyzer Queries and Run-time Details

Use the list command in the following procedure to list saved queries and run-time details to the screen. For information about running the Log File Analyzer (LFA), see About Running Log File Analyzer Commands. For information about creating saved queries, see Creating and Saving LFA Queries.

For information about each list item, see Listing Log File Information Using Log File Analyzer for details.

To list Log File Analyzer queries and run-time details

• Enter:

  list list_item
  

  In this command, list_item is the list item of interest.

For items available for listing, see the following table.

Item	Description
all	Lists all LFA items available for listing. Note: The LFA does not list users or sessions until you perform at least one user query.
queries	Lists LFA queries saved in the current session.
servers	Lists servers searched by LFA.
sessions	Lists sessions found in the log files searched by LFA.
plugins	Lists instances of Siebel Application Interface searched by LFA.
components	Lists components with information in log files searched by LFA.
processes	Lists processes with information in log files searched by LFA.
users	Lists users with information in the log files searched by LFA.

Note: If the LFA is not searching the appropriate server or Siebel Application Interface, then see Configuring the Log File Analyzer for details on configuring the LFA to search the server and Siebel Application Interface of interest.

Listing Log File Information Using Log File Analyzer

Use the info command in the following procedure to list detailed information on the values of the run-time details. For a list of items available for use with the info command, see Listing Log File Analyzer Queries and Run-time Details.

For information about running the Log File Analyzer (LFA), see About Running Log File Analyzer Commands. For information about creating saved queries, see Creating and Saving LFA Queries.

To list information on values for Log File Analyzer run-time details

• Enter:

  info info_item
  

  In this command, info_item is the value of a list item of interest.

For items available for listing (with the exception of list item all and queries), see the table in Listing Log File Analyzer Queries and Run-time Details.

List information on multiple list values by separating values with a comma or space for the info_item parameter.

For example, using the list command for users revealed an entry named asmith. Use the following command to list information on asmith:

info asmith

Exiting Log File Analyzer

Use the following command to exit the log file analyzer. Exiting the log file analyzer deletes saved queries for that session unless query output is saved to text files. For information about this task, see Saving Log File Analyzer Output to Text Files.

To exit the Log File Analyzer

• Enter:

  exit
  

Troubleshooting Log File Analyzer Errors

This topic provides guidelines for resolving errors and problems that the Log File Analyzer (LFA) might generate during processing. To resolve the problem, look for it in the Symptom/Error Code and Message column in the following table.

System or Error Code and Message	Diagnostic Steps or Cause	Solution
SBL-LFA-00100 Section [%s] in configuration file is empty.	The section indicated in the error message is blank. LFA requires content for this section.	For the correct specification of the configuration file, see Configuring the Log File Analyzer.
SBL-LFA-00101 Rule "%s" appears in the configuration file but is not registered.	A rule has been added to the LFA configuration file but not registered with the utility. Therefore, the rule is not recognized.	At this time, it is not possible to create customized rules for the LFA. Remove this rule from the configuration file.
SBL-LFA-00102 Cannot find section [%s] in the configuration file.	Though it is a required section, the section of the LFA configuration file indicated in the error message text is missing.	For the correct specification of the configuration file, see Configuring the Log File Analyzer.
SBL-LFA-00103 There is a format problem in section [%s] of the configuration file.	There is a formatting error in the LFA configuration file section indicated in the error message text.	For the correct specification of the configuration file, see Configuring the Log File Analyzer.
SBL-LFA-00104 Value "%s" in the section is invalid or missing.	There is a missing value in the LFA configuration file section indicated in the error message text.	For the correct specification of the configuration file, see Configuring the Log File Analyzer.
SBL-LFA-00105 Time filters are invalid or have contradictory values.	The time filter you are trying to use in your query is invalid. It is possible that the To time is before the From time.	For information about using time filters correctly, see Querying Log Files Within a Time Interval.
SBL-LFA-00106 Value or Name for "%s" is a negative number.	This value is not expected to be negative.	Provide a positive value.
SBL-LFA-00107 Cannot open file: "%s".	The LFA cannot write output to the given file.	Check your permissions to the file and directory. Make sure the file is not read only.
SBL-LFA-00108 File "%s" is already in use.	This file might be locked by another running application.	Shut down applications that might be accessing the file and try again.
SBL-LFA-00109 Cannot create pipe for command \"%s\".	Pipe is not supported.	This functionality is not supported.
SBL-LFA-00110 OUT OF MEMORY !!!!!!	The computer on which you are using the LFA has run out of memory.	Shut down some of your applications and try again.
SBL-LFA-00112 Query's "where" clause is invalid.	The where clause in the query is not correctly specified.	For information about correct application of the WHERE clause, see Creating and Saving LFA Queries.
SBL-LFA-00113 Query with name "%s" does not exist.	You have tried to reference a query that does not exist.	Type list queries to see existing queries. If your query does not exist, then you must create it before trying to reference it. For information about creating queries, see Creating and Saving LFA Queries.
SBL-LFA-00114 Filter for "%s" does not exist.	The specified parameter cannot be used as a filter.	Do not use this item as a query parameter.
SBL-LFA-00115 Category "%s" does not exist.	You tried to use the specified word, but only key words are expected	Fix the command and try again. For information about key words, see Listing Query Command Key Words.
SBL-LFA-00116 Object "%s" does not exist.	The object (that is, Siebel Server, Siebel Application Interface, query, user, component, or session) that you are trying to reference is unavailable.	Make sure the object is available for reference. For information about listing existing objects, see Listing Log File Analyzer Queries and Run-time Details.
SBL-LFA-00117 Object "%s" already exists. Please use another name.	An object by that name already exists.	Use another name for your object.
SBL-LFA-00118 Query "%s" finished abnormally.	The query finished abnormally, possibly due to corrupt log files or user intervention.	Re-run the query. If that does not work and the query is complex, then try simplifying it.
SBL-LFA-00119 "%s" should not be used for naming.	The name you have specified cannot be used.	Use another combination of characters.
SBL-LFA-00120 Cannot interpret: "%s"	The name you have specified cannot be used in this place.	The LFA identified an error in your command syntax. For information about valid LFA commands, see About Running Log File Analyzer Commands.
SBL-LFA-00121 Token has a wrong value: "%s"	The specified value is invalid.	For information about valid LFA commands, see About Running Log File Analyzer Commands.
SBL-LFA-00122 Unknown issue.	There is an error in the command that you have entered.	For information about valid LFA commands, see About Running Log File Analyzer Commands.
SBL-LFA-00123 There is no file "%s".	The input file that you specified when starting the LFA does not exist.	Make sure the file exists and the filename and path is correct.
SBL-LFA-00124 Wrong format of the string: "%s".	The specified string is formatted incorrectly.	For information about valid LFA commands, see About Running Log File Analyzer Commands.
SBL-LFA-00125 Error parsing configuration file "%s".	The Log File Analyzer configuration file specified in the message text is missing.	Restart the LFA with another configuration file, or make sure the specified configuration file is available.
SBL-LFA-00126 Too many unrelated files are found following main server log file pattern: "%s".	The log files in the server log directory are inconsistent. More than one unrelated file fits the main server log file pattern that is used by the LFA to initialize the server model.	Remove all unrelated files and try again.
SBL-LFA-00127 Invalid usage of the command.	You have used the command incorrectly.	For information and links to the correct usage of LFA commands, see About Running Log File Analyzer Commands.
SBL-LFA-00128 Component with name "%s" could not be found.	The Log File Analyzer cannot translate the component name you entered into a component short name.	If this is a valid component, then specify its short name in the LFA configuration file. For more information, see Configuring the Log File Analyzer.
SBL-LFA-00130 Language "%s" could not be initialized. Please see Log File Analyzer documentation for more information.	The language files in the locale directory on the Siebel Server might be missing or corrupt.	Review information about LFA log file language considerations. For more information, see About the Log File Analyzer.
SBL-LFA-00131 String with code "%s" could not be loaded. Please see Log File Analyzer documentation for more information.	The language files in the locale directory on the Siebel Server might be missing or corrupt.	Review information about LFA log file language considerations. For more information, see About the Log File Analyzer.
SBL-LFA-00132 Formatting string "%s" is not supported. Parameters for this string could not be extracted.	An error in the string makes it impossible for the Log File Analyzer to parse it properly.	If you cannot resolve the underlying issue that caused this error, then contact Oracle Global Customer Support by creating a service request (SR) on My Oracle Support.