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:
PROCESS defaults to
For example, the log files for a Siebel 8.0 development environment upgrep appear in the following locations:
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:
The Logparse Utility
For each upgrade process, the Logparse utility analyzes the log files in
process. It then summarizes the log files and provides several reports. The Logparse reports provide the following information:
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.
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.
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.