Upgrade Guide > Reviewing the Siebel Upgrade Log Files >

Summarizing Siebel Log Files Using Logparse

Upgrades: All Siebel upgrades.

Environments: Development, production test, production.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

Use the log parse utility to create summary.txt and summary.html, a browser-based summary of all files in the log output directory. Use the summary file to review database process log files, verify parameters, review errors, and identify costly SQL and DDL steps.

To execute the log parse utility

1. Navigate to the following directory:

   Windows: SIEBEL_ROOT\bin

   UNIX: $SIEBEL_ROOT/bin

2. Run the following command. Use the syntax in Table 33:

   logparse /s install_dir /g LANGUAGE_CODE /r PROCESS /l LOGPARSE_FILENAME
/n MAX_NUMBER_SQL /t THRESHOLD_TIME /e MAX_NUMBER_ERRORS

Windows example (language is English):

logparse /s C:\sea7xx /g enu /r upgrep_dev_704 /l logparse.log /n 10 /t 00:00:10 /e 5

The summary.html file automatically opens for your review if you executed the log parse utility for a single database process (that is, if you used the command line flag /r PROCESS, where PROCESS=UPGRADEOPTION_ENVIRONMENT_VERSION).

If you executed the log parse utility for all processes in the output directory (that is, if you used the command line flag /r ALL), you must manually open the summary file that you want to review.

Log files appear in your primary language, but summary.html appears only in English (enu).

To review the summary.html or summary.txt file

1. If the summary file is not already open, open summary.html from the following directory:

   Windows: SIEBEL_ROOT\log\PROCESS

   UNIX: $SIEBEL_ROOT/log/PROCESS,

   Where:

   PROCESS is the database process you want to review.

   UNIX: If a browser is not installed on the machine you are using, open summary.txt from $SIEBEL_ROOT/log/PROCESS.

2. Review the parameters to make sure they are correct.
   • If you are reviewing summary.html, select the Parameters link to review your upgrade parameters.

     When you are finished, click Back to return to the summary screen.

   • If you are reviewing summary.txt, scroll down to review your upgrade parameters.

     Passwords are encrypted.

3. Review the step details for errors.
   • If you are reviewing summary.html, select the Steps/Errors link, then scroll down the page to review the step details for errors.
     • If no errors occurred for a step, then the step detail displays Errors:None.
     • If more than five errors occurred for a step, the number of errors found appears as a link. Click the link to review all errors for that step.
   • If you are reviewing summary.txt, scroll down to review the step details for errors.

     If more than five errors occurred for a step, you must manually review the log files.

     Summary.html and summary.txt only identify errors encountered by the ODBC driver for the database. Summary.html does not identify errors from Siebel utilities. To determine if errors were encountered by Siebel utilities, review the log files for these utilities.

4. For every error found, determine whether it is an acceptable error by following the procedure Reviewing Siebel Upgrade Log Files for Errors.

   If you are reviewing summary.html, click Back to return to the summary screen.

5. Identify SQL steps that have the greatest performance impact by selecting the Performance Information for SQL link in summary.html or by scrolling down to the following sections in summary.txt:
   • Longest-running queries (based on the criteria you defined using the /t command line option)
   • Queries that returned zero rows (based on the criteria you defined using the /n command line option)
   • If a group of steps are executed in parallel, only the duration time of the longest step is added to the total process time. This means that the sum of durations from parallel-step logs will be less than the duration shown in summary.html (summary.txt).

     If you are reviewing summary.html, click Back to return to the summary screen.

6. Review the performance impact caused by table and index creation.
   • If you are reviewing summary.html, select the Performance Information for DDL link to review performance information.

     This page may take a while to load due to its large size.

   • If you are reviewing summary.txt, scroll down to review performance information.

     If no information is available, then the process did not execute DDL.

7. Resolve any errors that occurred and, if necessary, restart the upgrade.