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

Troubleshooting the Siebel Database Schema Upgrade

Typical problems that might occur during the upgrade of your Siebel Database Schema could result from a lack of storage space or insufficient user privileges.

Recovering from a Failed Siebel Database Schema Upgrade

If the repository upgrade fails due to insufficient space allocated on the database, you must complete the following procedures.

To recover from a failed Siebel database schema upgrade

  1. Back up your complete set of log files, from the beginning of the upgrade process to the point at which it stopped, to another directory.
  2. Read the srvrupgwiz1.log file and associated log files to determine the failure. See Reviewing the Upgrade Log Files.
  3. Take the necessary corrective action. Depending on the errors that you find, you may need to ask your DBA to extend the database.
  4. Resume the upgrade wizard. It will continue from the point at which it failed.

    To resume the upgrade wizard, navigate to $SIEBEL_ROOT/siebsrvr/bin and type:

    srvrupgwiz /m master_UPGRADEOPTION_ENVIRONMENT_VERSION.ucf

    For example, to restart a development environment upgrade from Release 6.0.1 to Release 7.x, type:

    srvrupgwiz /m master_upgrep_dev_601.ucf

Restarting the Upgrade

The Siebel Upgrade Wizard is restartable at most stages within the upgrade process. If the Siebel Upgrade Wizard encounters an error during the upgrade process, it stops at that point. If your upgrade stops due to an error, perform the following steps.

To restart the upgrade

  1. Carefully review the relevant log files to make sure that your upgrade has completed successfully up to that point.
  2. Before you restart the upgrade (after any break in the upgrade process) back up your complete set of log files, from the beginning of the process to the point at which it stopped, to another directory. This maintains a complete record of your log files, and prevents your previous log files from being overwritten, which could prevent accurate diagnosis of the reason for the break in the upgrade.
  3. After you resolve the failure, you may restart the upgrade. The upgrade continues from the last step that completed successfully.

If problems with your environment prevent the upgrade from restarting, you need to restore the database from the prior base version (the version which you are upgrading from). For example, environment problems may occur when table creation fails due to a database problem (insufficient storage or network problems), which cause subsequent upgrade steps to fail. If you need to restore your database and restart the upgrade, you should delete or store the upgrade log files that were generated under $SIEBEL_ROOT/siebsrvr/log/PROCESS/output to a zip file. You should also delete the log file, state.log, from $SIEBEL_ROOT/siebsrvr/log/PROCESS/state.

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

Launching the Siebel Upgrade Wizard

The Siebel Upgrade Wizard launches from the final prompt of the Database Server Configuration Utility. However, if a program or system error occurs and you need to rerun the Siebel Upgrade Wizard, you can do so, starting at the point at which the wizard failed, by using the following procedure.

To relaunch the Siebel Upgrade Wizard or to restart the upgrade

  1. Navigate to $SIEBEL_ROOT/siebsrvr/bin and type the following command:

    srvrupgwiz /m master_UPGRADEOPTION_ENVIRONMENT_VERSION.ucf

    For example, to restart a development environment upgrade from Release 6.0.1 to Release 7.x, type the following command:

    srvrupgwiz /m master_upgrep_dev_601.ucf.

  2. To begin the upgrade of your repository, at the prompt, press Enter.

    The Siebel Upgrade Wizard will notify you when the upgrade process is complete.

You have finished upgrading your repository and are ready to review the log files for errors. See Reviewing the Upgrade Log Files.


 Upgrade Guide for UNIX
 Published: 20 October 2003