Upgrade Guide > Reviewing the Siebel Upgrade Log Files >

Reviewing Siebel Upgrade Log Files for Errors

Upgrades: All Siebel upgrades.

Environments: Development, production test, production.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

Do not proceed with the upgrade until unacceptable errors have been corrected. If you cannot correct the error, contact Oracle's Siebel Technical Support or Professional Services to report the error in detail.

The log files may include errors that are expected and benign. Before you continue with the upgrade, you must compare any error messages found in the log files to a list of acceptable error messages.

If you encountered an error during the upgrade, review log files named UpgWiz.log (Windows) or srvrupgwiz1.log (UNIX). The log file is located in the following directory:

Windows: SIEBEL_ROOT\log\PROCESS\output

UNIX: $SIEBEL_ROOT/log/PROCESS/output

The name of the log file increments for subsequent log files that are created when the upgrade wizard encounters a problem and the user runs the 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.

Some Log Files 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, srvrupgwiz1_01.log, and srvrupgwiz1_02.log
• Any other log file that existed before the start of the upgrade

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

Related Topics

Summarizing Siebel Log Files Using Logparse

Troubleshooting Steps 19: How To Troubleshoot Messages Generated During the Repository Merge in Siebel 7, located on Oracle's Siebel SupportWeb

Troubleshooting Steps 21: How to troubleshoot messages generated while running the Repository Upgrade in Siebel v7

Troubleshooting Steps 28: Errors.rtf -- Siebel version 7.5.3

Reviewing the Log Files

To manually review the log files for unacceptable errors

1. Review the state1.log file to see at what step the upgrade failed. This step can be traced back to the driver file. The state1.log file is located in the following directory:

   Windows: SIEBEL_ROOT\log\PROCESS\state

   UNIX: $SIEBEL_ROOT/log/PROCESS/state

2. Print the errors file. This file is located in the installation subdirectory for your database platform:

   Windows: DBSRVR_ROOT\DATABASE_PLATFORM\errors.rtf or errors.htm

   UNIX: DBSRVR_ROOT/DATABASE_PLATFORM/errors.txt

3. Sort the files in the following directory by date.

   Windows: SIEBEL_ROOT\log\PROCESS\output

   UNIX: $SIEBEL_ROOT/log/PROCESS/output

4. Open each log file, starting with the earliest, and search for errors.

   Log files are identified by the .log extension. Errors are either tagged with the word "error" or enclosed in square brackets "[...]."

   You must start with the earliest log file to shorten your research time if you find unacceptable errors in an early log file.

5. For each error found, compare the error description against the list of acceptable errors documented in the errors file.

   The log files generated by the repository upgrade wizard (for example srvrupgwiz1.log) appear in the errors file as upgwiz1.log, upgwiz2.log, incrementing for additional log files.

   • If you find the error in the errors file, it is acceptable and no action is required. Continue to review the errors found in the log file.
   • If an error appears multiple times in a log file, but only one occurrence of that error appears in the errors file, all errors of that type are acceptable and no action is required. Continue to review the errors found in the log file.
   • If a log file is not listed in the errors file, there are no acceptable error messages for that log file. You must correct the condition that caused the error before you rerun the Upgrade Wizard.
   • If you find an error that is not listed in the errors file, it is unacceptable. You must correct the condition that caused the error before you rerun the Upgrade Wizard.

     On Oracle's Siebel SupportWeb, navigate to Troubleshooting Steps > Product Areas > Upgrade, and choose Troubleshooting Steps 21. Common errors and how to resolve them are listed in this document. If the error is not listed or you cannot resolve it, contact Oracle's Siebel Technical Support. Do not proceed with the upgrade.

6. Repeat the previous step for each log file.

Although other errors are rarely encountered, this review is critical. Certain errors, such as a failure to create indexes, may result in performance problems or anomalous behavior in Siebel Business Applications.