1. Database Upgrade Guide
  2. Upgrade Wizard 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

In these paths, PROCESS specifies UPGRADEOPTION_ENVIRONMENT_VERSION by default.

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

  • Windows: SIEBEL_ROOT\log\upgrep_dev_versionnumber

  • UNIX: $SIEBEL_ROOT/log/upgrep_dev_versionnumber

You can select a different directory for the log files, by specifying a value for the Log Output Directory option in the Database Configuration Wizard. This option is for specifying a different subdirectory, under the log directory, in which to create the log files.

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_ROOT\platform\upgrade\version. An example of a driver file: driver_upgrep_dev_811ucf. The Upgrade Wizard performs the steps in the driver file. If a step calls a utility, such as ddlimp or dataimp, then the /l option in the command syntax specifies the name of the log file. Unless you modified the output location for the log file, it is located at 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 HTML file is created by the Logparse utility. It summarizes the log files in the outputdirectory. Use this file to verify that all upgrade steps completed successfully and to determine whether there were any errors.

    • summary.txt. This text file is created by the Logparse utility. This file contains the same information as summary.html.
      Note: If a browser is not installed on the computer you are using, then review summary.txt instead of summary.html.

    • summary.xml. This file is 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). This file is produced by the Logparse utility during production upgrades. You can use this file to transfer the upgrade scripts from your UNIX computer to a Windows temporary directory to perform upgrade tuning. (Development upgrades do not produce upgtuner_ftp_get.txt.)

    • upgtuner_ftp_put.txt. (UNIX Only). This file is 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 computer back to your UNIX environment. (Development upgrades do not produce upgtuner_ftp_put.txt.)