Bookshelf Home | Contents | Index | Search | PDF

Upgrade Guide for UNIX > Upgrading the Siebel eBusiness Application > Reviewing the Upgrade Log Files >

Reviewing the Log Files for Unacceptable Errors

---

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 srvrupgwiz1.log, srvrupgwiz2.log (and so on) in the $SIEBEL_ROOT/siebsrvr/log/PROCESS/output directory. The name of the log file increments for subsequent log files that are created when the upgrade wizard encounters a problem and the user attempts a retry.

  NOTE:  If you are upgrading to a version prior to Release 7.5.3, the log files are located in the $SIEBEL_ROOT/siebsrvr/log directory.

  Review the end of the srvrupgwiz 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 srvrupgwiz 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.

• If the upgrade completed successfully, there are several log files that you can safely ignore:
  • siebel.log, siebel_01.log, siebel_**.log
  • srvrupgwiz_01.log, srvrupgwiz_**.log
  • Any other log file that existed prior to the start of the upgrade

    NOTE:  Pay attention to log file names, because there are similarly named log files that you do need to review: srvrupgwiz1.log, srvrupgwiz2.log, and subsequent 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 $SIEBEL_ROOT/siebsrvr/log/PROCESS\state.
2. Print the errors.txt file. This file is located in the installation subdirectory for your database platform ($DBSRVR_ROOT\DATABASE_PLATFORM).
3. Sort the files in the $SIEBEL_ROOT/siebsrvr/log/PROCESS/output directory according to date. Under both Solaris and AIX, sort the files by entering the command: ls -ltr

   NOTE:  It is important that you start with the earliest log file to shorten your research time if you find unacceptable errors in an early log file.

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 "[...]."
5. For each error found, compare the error description against the list of acceptable errors documented in errors.txt.

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

   • If you locate the error in errors.txt, 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 errors.txt, 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 errors.txt, 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.txt file, it is unacceptable. You must correct the condition that caused the error before you rerun the Upgrade Wizard.

     Report the error to Siebel Technical Support. Do not proceed with the upgrade.

6. Repeat the previous step for each log file.

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

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 eBusiness Applications.

Bookshelf Home | Contents | Index | Search | PDF