Upgrade Guide for DB2 UDB for z/OS and OS/390 > Reviewing the Database Upgrade Log Files >

About the Database Upgrade Logs

Upgrades: All upgrades.

Environments: All environments.

The Siebel Upgrade Wizard produces all log files for a given process in one directory.

Windows: SIEBEL_ROOT\log\PROCESS

UNIX: $SIEBEL_ROOT/log/PROCESS

where PROCESS defaults to UPGRADEOPTION_ENVIRONMENT_VERSION.

For example, all log files for a Siebel Database schema upgrade of a development environment from Release 7.0.4 appear in the following locations:

Windows: SIEBEL_ROOT\log\upgrep_dev_704_mf

UNIX: $SIEBEL_ROOT/log/upgrep_dev_704_mf

All log files for the production upgrade process appear in the following directory:

Windows: SIEBEL_ROOT\log\upgrep_prod_704_mf

UNIX: $SIEBEL_ROOT/log/upgrep_prod_704_mf

You can select a different directory from the Log Output Directory screen in the Database Server Configuration utility.

The log file directory contains the following files and subdirectories:

• Output. Directory containing process log files.
• State. Directory containing the state.log file.

  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. Directory that contains the source files for summary.html.
• Summary.html. Browser-based file that summarizes the log files in the output directory.
• Summary.txt. Text file that summarizes the log files in the output directory.

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

• Summary.xml. File produced during production upgrades and used by the Siebel Upgrade Tuner to parallelize table creation and index creation and inactivate SQLs that affect no rows. (Development upgrades do not produce a summary.xml file.)
• Upgtuner_ftp_get.txt (UNIX Only). File produced 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 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.)