Upgrade Guide for UNIX > Upgrading the Siebel eBusiness Application > Upgrading the Custom Database Schema >

Troubleshooting the Custom Database Schema Upgrade

Typical problems that might occur during the upgrade of your custom database schema could result from a lack of storage space or insufficient user privileges.

Recovering from a Failed Custom 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 custom 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_upgphys_dev_601.ucf


 Upgrade Guide for UNIX
 Published: 20 October 2003