Siebel Database Upgrade Guide > Upgrading the Siebel Database >

Starting the Siebel Upgrade Wizard

Environments: Development, production test, production.

The Siebel Upgrade Wizard executes the upgrade of the Siebel database. It takes a master configuration file as input. This file contains environment information and a driver file name. The Upgrade Wizard executes the steps in the driver file to perform the upgrade.

As the Upgrade Wizard performs the steps in the driver file, it lists the steps in a state log. The state log is located in siebsrvr/LOG/process/state, where process is the upgrade process, for example upgrep_prod_811 (upgrade from 8.1.1, upgrep process, production test or production environment).

If the Upgrade Wizard encounters an error and exits during an upgrade, then you can restart it after correcting the error. The Upgrade Wizard reads the state log and continues the upgrade from the last successfully completed step.

When you run the Database Configuration Utilities on Windows, they will prompt you if you want to start the Upgrade Wizard. When you run the Database Configuration Utilities on UNIX, you must start the Upgrade Wizard manually.

Requirements for Restarting the Upgrade Wizard

If the Upgrade Wizard stops due to errors, then verify that you have met these requirements before restarting the wizard:

• Carefully review the relevant log files to make sure that your upgrade has completed successfully up to that point.
• 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 backup 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.

• If you are continuing a previous and incomplete schema upgrade, then do not change the Log Output Directory that you previously selected.
• If problems with your environment prevent the upgrade from restarting, then you must restore the database from the prior base version (the version from which you are upgrading). For example, environment problems might occur when table creation fails due to a database problem (insufficient storage or network problems), which cause subsequent upgrade steps to fail.

  If you must restore your database and restart the upgrade, then delete or store the upgrade log files. The files are located in the following directory:

  Windows: SIEBEL_ROOT\log\PROCESS\output

  UNIX: $SIEBEL_ROOT/log/PROCESS/output

  Also delete the state.log file. It is located in the following directory:

  Windows: SIEBEL_ROOT\log\PROCESS\state

  UNIX: $SIEBEL_ROOT/log/PROCESS/state

Starting the Upgrade Wizard

Use this procedure to start the Upgrade Wizard. See the following topics to stop the Upgrade Wizard, Stopping the Upgrade Wizard on Windows and Stopping the Upgrade Wizard on UNIX.

To start the Upgrade Wizard

1. Navigate to the following directory:

   Windows: SIEBEL_ROOT\bin

   UNIX: $SIEBEL_ROOT/bin

2. Enter the following command:

   Windows: siebupg /m master_UPGRADEOPTION_ENVIRONMENT_VERSION.ucf

   UNIX: srvrupgwiz /m master_UPGRADEOPTION_ENVIRONMENT_VERSION.ucf

   In these commands, UPGRADEOPTION_ENVIRONMENT_VERSION is the portion of the upgrade configuration file name that lists upgrade process, upgrade environment, and the Siebel CRM release (version) from which you are upgrading. The file is located in SIEBEL_ROOT\bin (UNIX: $SIEBEL_ROOT/bin).

   Numbers like the following examples are used for the Siebel CRM release portion of the file name:

   • 78
   • 80
   • 811 (SEA)

     Table 24 lists an example of the file names for an upgrade from Siebel CRM version 8.0.

     Table 24. Example of File Names for an Upgrade from Siebel CRM 8.0

     Upgrade Mode	File Name
     Development environment upgrep	master_upgrep_dev_80.ucf
     Development environment upgphys	master_upgphys_dev_80.ucf
     Additive Schema Changes	master_additive_gen.ucf
     Prepare for Production	master_prepare_for_production_upgrade.ucf
     Production environment upgrep and upgphys	master_upgrep_prod_80.ucf

3. To begin the upgrade, click OK (Windows) or press Enter (UNIX).

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

Stopping the Upgrade Wizard on Windows

Do not stop the Upgrade Wizard unless you are confident that an error has occurred, and the Upgrade Wizard or a utility it has called is hanging. Some SQL commands issued by the Upgrade Wizard or by its utilities can take considerable time to complete.

If you are not sure whether the Upgrade Wizard is hanging, then create a service request (SR) on My Oracle Support, or contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services.

Stopping the Upgrade Wizard can have varying effects on the RDBMS. Before restarting the Upgrade Wizard, review the RDBMS log files. Run SQL commands as needed to resolve errors found in the RDBMS log files.

To stop the Upgrade Wizard on Windows

• Do one of the following:
  • If the Upgrade Wizard has launched a separate command window in which a utility is running, then close the command window. This terminates the utility and stops the upgrade.
  • In the Upgrade Wizard dialog box, click Cancel. The Upgrade Wizard will exit when the current upgrade step is complete. There might be a delay while the step completes in the RDBMS.

Stopping the Upgrade Wizard on UNIX

Do not stop the Upgrade Wizard unless you are confident that an error has occurred, and the Upgrade Wizard or a utility it has called is hanging. Some SQL commands issued by the Upgrade Wizard or by its utilities can take considerable time to complete.

If you are not sure whether the Upgrade Wizard is hanging, then create a service request (SR) on My Oracle Support, or contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services.

Stopping the Upgrade Wizard can have varying effects on the RDBMS. Before restarting the Upgrade Wizard, review the RDBMS log files. Run SQL commands as needed to resolve errors found in the RDBMS log files.

To stop the Upgrade Wizard on UNIX

1. If the Upgrade Wizard has started a utility in a child process, then stop the child process.
2. Exit the shell in which the Upgrade Wizard is running.
3. Locate and stop any orphaned child processes started by the Upgrade Wizard.

After the processes terminate, there might be a delay while the RDBMS executes the issued SQL commands.

Related Topics

About the Siebel Upgrade Wizard and Driver Files