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

About the Siebel Upgrade Log Files

The Upgrade Wizard writes logs that provide detailed information on the upgrade processes and they also list all errors. The Upgrade Wizard writes the logs for a process to the following directory by default:

Windows: SIEBEL_ROOT\LOG\process

UNIX: $SIEBEL_ROOT/log/process

where process is the name of the upgrade process you have run, for example, upgrep_dev_704 or prepare_for_production_upgrade.

The process directory contains the following subdirectories:

• Output. Directory containing the Upgrade Wizard log files
• State. Directory containing the state.log file

The output and state 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.

NOTE:  You can select a different log directory from the Log Output Directory screen on the Database Configuration Wizard.

About the State Log File

Each upgrade process consists of a series of steps, each of which must complete successfully. If the Upgrade Wizard cannot complete a step, it marks the step as incomplete in the state.log file and exits. The state.log file is located in SIEBEL_ROOT\LOG\process\state (Windows) or SIEBEL_ROOT/LOG/process/state (UNIX).

You must correct the error and then run the Upgrade Wizard again. When you rerun the Upgrade Wizard, it refers to the state log and resumes at the incomplete step that contained the error.

About Process Log Files

You can identify errors you encounter during an upgrade by reviewing the log file named UpgWiz.log (Windows) or srvrupgwiz1.log (UNIX) in the SIEBEL_ROOT\LOG\process\output directory (Windows) or the SIEBEL_ROOT/LOG/process/output directory (UNIX).

The name of the log file increments for subsequent log files that are created if the Siebel Upgrade Wizard encounters a problem and you run the Siebel Upgrade Wizard again.

Review the end of the log file for details about the latest failure. If the step that failed was not a native SQL step (which would be listed in the log file), then it occurred as part of an external utility for which you need to review a corresponding log file, identified by the /L parameter.

How to Determine if the Upgrade Process Completed Successfully

If the status of all the steps in the state.log is Complete, the upgrade process completed successfully.

If the status of any step is Incomplete, the upgrade process did not complete successfully. You must identify the error and correct it before resuming the upgrade.

NOTE:  In some cases, the Upgrade Wizard can complete a step even though the step contains unacceptable errors. You must verify that all steps do not contain unacceptable errors, even those with a status of Complete.

Use the following process to identify errors:

1. Resolve errors for steps identified with a Status of Incomplete in the state.log file.
2. Review all the steps with a status of Complete in the state.log file. If any contain unacceptable errors, resolve these errors. See Reviewing Siebel Upgrade Log Files for Errors for information on identifying unacceptable upgrade errors.
3. Restart the Upgrade Wizard, or, if necessary, restore the database and rerun the upgrade process.

If you have any questions regarding how to resolve errors, create a service request (SR) on My Oracle Support.

Log Files That Can Be Ignored

If the upgrade completed successfully, there are several log files that you can safely ignore:

• Windows: sw_cfg_xxx.log and siebel.log
• UNIX: srvrupgwiz_*.log and siebel_*.log. For example, srvrupgwiz_001.log, and srvrupqwiz1_02.log
• Any other log file that existed before the start of the upgrade

CAUTION:  UNIX Only: The log file srvrupgwiz_001.log is a different file than srvrupgwiz1.log. Do not ignore log files named srvrupgwiz1.log, srvrupgwiz1_01.log and so on.