Siebel Database Upgrade Guide > How the Siebel Database Upgrade Works >

About the Siebel Database Upgrade Log Files

Upgrades from: All Supported Siebel releases.

Environments: Development, production test, production.

Platforms: Windows and UNIX only. Does not apply to IBM z/OS.

The Upgrade Wizard writes log files that provide detailed information on the upgrade processes, for example development-environment upgrep and upgphys. These log files provide detailed information on the upgrade steps, and they also list all errors. The Logparse utility analyzes and summarizes these log files.

Upgrade Wizard Log Files

The Upgrade Wizard writes the log files for a process to the following directory:

Windows: SIEBEL_ROOT\log\PROCESS

UNIX: $SIEBEL_ROOT/log/PROCESS

where PROCESS defaults to UPGRADEOPTION_ENVIRONMENT_VERSION.

For example, the log files for a Siebel 8.0 development environment upgrep appear in the following locations:

Windows: SIEBEL_ROOT\log\upgrep_dev_80

UNIX: $SIEBEL_ROOT/log/upgrep_dev_80

You can select a different directory for the log files in the Log Output Directory screen in the Database Server Configuration Utilities.

Each subdirectory in the log directory contains the following files:

• Output. This subdirectory contains the Upgrade Wizard log files.
  • upgwiz.log (srvrupgwiz.log on UNIX). The Upgrade Wizard log for the process. This log contains detailed information on how the Upgrade Wizard ran. If you run the process more than once, the log name increments, for example upgwiz2.log or srvrupgwiz2.log.
  • Windows only. Log files with the name upgwizn(nnn) can be ignored. For example, upgwiz1(001).log, upgwiz1(002).log, and so on.
  • Windows only. Log files with the name sw_cfg_xxx can be ignored. (These are located in the log directory.)
  • UNIX only. Log files with the name srvrupgwizn_nnn can be ignored. For example, srvrupgwiz1_01.log, srvrupgwiz1_02.log, and so on.
  • Log files with the name siebel.log can be ignored.

    TIP:   Each upgrade process, for example, a development upgrep, has a driver file located in \dbsrvr\platform\upgrade\version. An example of a driver file: driver_upgrep_dev_77.ucf. The Upgrade Wizard performs the steps in the driver file. If a step calls a utility, such as ddlimp or dataimp, the /l option in the command syntax specifies the name of the log file. Unless you modified the output location for the log, $SiebelLogDir is \siebsrvr\log\process.

• State. This subdirectory contains the state.log file.
  • state.log. The state.log file lists each step in the upgrade process and whether the step completed successfully.

    The output and state log file directories are automatically archived on subsequent runs of a process that completes successfully. (The names of subsequent log directories are appended with _1, _2, and so on.) To preserve disk space, periodically delete or save log directories to another location.

• Summary. This subdirectory is generated by the Logparse utility. The Logparse utility also generates a report that summarizes the upgrade, summary.html. The summary.html file contains links to the html pages in the summary subdirectory.
• Summary.html. This file is created by the Logparse utility. It summarizes the log files in the output directory. Use this file to verify that all upgrade steps completed successfully and to determine if there were any errors.
• Summary.txt. Text file created by the Logparse utility. This file contains the same information as summary.html.

  NOTE:  If a browser is not installed on the machine you are using, review summary.txt instead of summary.html.

• Summary.xml. File produced by the Logparse utility during production upgrades and used by the Siebel Upgrade Tuner to parallelize table creation and index creation and to inactivate SQLs that affect no rows. (Development upgrades do not produce a summary.xml file.)
• Upgtuner_ftp_get.txt. (UNIX Only). File produced by the Logparse utility during production upgrades. You can use this file to transfer the upgrade scripts from your UNIX machine to a Windows temporary directory to perform upgrade tuning. (Development upgrades do not produce upgtuner_ftp_get.txt.)
• Upgtuner_ftp_put.txt. (UNIX Only). File produced by the Logparse utility during production upgrades. After you tune your production upgrade scripts, you can use this file to transfer the upgrade scripts from the temporary directory on your Windows machine back to your UNIX environment. (Development upgrades do not produce upgtuner_ftp_put.txt.)

The Logparse Utility

For each upgrade process, the Logparse utility analyzes the log files in siebsrvr\log\process. It then summarizes the log files and provides several reports. The Logparse reports provide the following information:

Parameters report

The Parameters report lists the total time required for the upgrade process. It also lists environment variables and input files used by the upgrade process. Use this report to verify that the upgrade was set up correctly.

Step/Error Summary

The Step/Error Summary lists each step in the upgrade process and whether it completed successfully. It also provides a link to a detailed step summary for each step.

The detailed step summary lists database errors returned by the Upgrade Wizard, SQL scripts, and errors returned by the upgrade utilities called by the driver files, such as ddlimp, and dataimp.

For Oracle Database and IBM DB2, the detailed step summary lists only unacceptable errors that must be corrected. The summary does not list benign errors.

For MSSQL, the detailed step summary lists all errors, including benign errors. An errors file (errors.xls and errors.rtf) is provided that lists benign errors for each database type. When you find an error in the summary.html file, you must compare it with the error file to determine if it is benign.

Performance report

The performance report provides a list of the longest running SQL scripts and a list of SQL scripts returning 0 rows. The lists include a link to each script. Upgrade Tuner uses this information as input to help you tune upgrade performance.

The report also provides two lists of DDL commands executed during the upgrade process. The DDL Summary lists the tables that were created, altered, or deleted by the ddlimp utility. The Native DDL Summary lists tables that were created, altered, or deleted by SQL scripts and includes a link to each script.