Bookshelf Home | Contents | Index | Search | PDF

Upgrade Guide for Microsoft Windows > Upgrading the Siebel eBusiness Application > Reviewing the Upgrade Log Files >

Summarizing the Log Files

---

Use the log parse utility to create 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.

NOTE:  If you are upgrading from Release 7.5.2 and you plan to use database utilities to synchronize DDL or migrate a repository from development to production, rerun the Database Server Configuration Utility to create a new version of the UCF file. Save this UCF file to use when you run database utilities.

This step avoids encountering an error message when you run the logparse.exe utility that the UCF file is not compatible.

To execute the log parse utility

• Type the following command from SIEBEL_ROOT/siebsrvr/bin using the parameters specified in Table 16:

  logparse.exe /s SIEBEL_ROOT /g LANGUAGE_CODE /r PROCESS /l LOGPARSE_FILENAME /n MAX_NUMBER_SQL /t THRESHOLD_TIME /e MAX_NUMBER_ERRORS

  Table 16.  Command Line Flags for Logparse.exe

  Flag	Parameter	Description	Comment
  /s	SIEBEL_ROOT	Siebel root directory.	Required
  /g	LANGUAGE_CODE	The language code for the log files, for example, enu.	Required
  /r	PROCESS	Name of the schema process for which you want a summary generated, for example, upgrep_dev_601.	Default value=ALL (creates summary files for all processes in the output directory)
  /l	LOGPARSE_FILENAME	Name of the log parse log file.	Default=logparse.log
  /n	MAX_NUMBER_SQL	Maximum number of longest-running SQLs to display in the summary.	Default value=10
  /t	THRESHOLD_TIME	Threshold time for longest running SQLs, in the format hh:mm:ss.	Default value= 00:10:00 (By default, SQLs that run longer than 10 minutes are displayed)
  /e	MAX_NUMBER_ERRORS	Maximum number of errors to display in the summary.	Default = 8 A hyperlink appears if you receive more errors

  Example

  logparse.exe /s SIEBEL_ROOT /g enu /r upgrep_dev_601 /l logparse.log /n 10 /t 00:00:10 /e 5

The log parse utility creates summary.html in the following directory: SIEBEL_ROOT\siebsrvr\log\PROCESS.

The summary file automatically opens 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 need to manually open the summary file that you want to review.

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

To review the summary.html file

1. If the summary file is not already open, open summary.html from SIEBEL_ROOT\siebsrvr\log\PROCESS, where PROCESS is the database process you want to review.
2. Select the Parameters hyperlink, then review the parameters to make sure they are correct.

   NOTE:  Passwords are encrypted.

   Click the back button to return to the summary screen.

3. Select the Steps/Errors hyperlink, 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 hyperlink. Click the hyperlink to review all errors for that step.

     NOTE:  Summary.html only identifies errors encountered by the ODBC driver for the database.

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

   Click the back button on summary.html to return to the summary screen.

5. Select the Performance Information for SQL hyperlink, to identify SQL steps that have the greatest performance impact:
   • 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

     Click the back button to return to the summary screen.

6. Select the Performance Information for DDL hyperlink, to review the performance impact caused by table and index creation.

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

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

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

Bookshelf Home | Contents | Index | Search | PDF