Upgrade Guide for DB2 UDB for z/OS > Upgrading a Database from the Mainframe >

Resuming the Siebel Upgrade Wizard on the Midtier After the Third Pause

Upgrades: All upgrades.

Environments: Development (mainframe-centric) environment and Production environment.

This topic is part of an upgrade process. See How to Perform the Upgrade.

Once you have completed the tasks outlined in Executing the Upgrade on the z/OS Host (Phase 2 of 2) and have completed the task in Performing Intersection Table Maintenance (Production environment), continue the upgrade from the point at which it paused.

To resume the Siebel Upgrade Wizard on the midtier after the third pause

1. Resume the upgrade using the appropriate method for your operating system.

   Windows:

   • If the dialog box is still open from Step 2, click Yes in the dialog box for Pause #3.
   • If you closed the Siebel Upgrade Wizard screen or it is no longer open, restart the upgrade by typing the following command at the Windows DOS command prompt from the SIEBEL_ROOT\BIN directory:

   siebupg.exe /m master_UPGRADEOPTION_ENVIRONMENT_VERSION_mf.ucf

   For example, to restart a development environment upgrade from Release 7.0.4, enter the following command:

   siebupg.exe /m master_upgrep_dev_704_mf.ucf

   To restart a production environment upgrade from Release 7.0.4, enter the following command:

   siebupg.exe /m master_upgrep_prod_704_mf.ucf

   UNIX:

   • Navigate to $SIEBEL_ROOT/bin and enter the following command:

   srvrupgwiz /m master_UPGRADEOPTION_ENVIRONMENT_VERSION_mf.ucf

   For example, to restart a development environment upgrade from Release 7.0.4, enter the following command:

   srvrupgwiz /m master_upgrep_dev_704_mf.ucf

   To restart a production environment upgrade from Release 7.0.4, enter the following command:

   srvrupgwiz /m master_upgrep_prod_704_mf.ucf

2. In the Siebel Upgrade Wizard screen, select Yes to resume the upgrade.

   NOTE:  When you are performing a development environment upgrade, the Siebel Upgrade Wizard may stop responding during the Repository Data Upgrade step. If this happens, cancel the Siebel Upgrade Wizard and, from the command prompt, navigate to $Siebsrvr\Bin and execute the RUNSTATS commands on tables S_COLUMN and S_UK_ATTJOIN using the following syntax:
   
   RSTAT390 /u <database_username> /p <database_password> /c <ODBC datasource> /d <Tableowner> /a Y /l <logfile> /T S_COLUMN
   
   RSTAT390 /u <database_username> /p <database_password> /c <ODBC datasource> /d <Tableowner> /a Y /l <logfile> /T S_UK_ATTJOIN

   After executing the these commands, restart the Siebel Upgrade Wizard from the command prompt by entering siebupg.exe /m master_upgrep_dev_<version>_mf.ucf.

   The remaining upgrade jobs run on the midtier. A check mark appears beside each item on the Upgrade Wizard screen as it is completed.

   CAUTION:  The upgrade process executes in a DOS command window. Do not click inside this window while the upgrade is running. If you accidentally click inside the DOS command window, the process pauses and the word Select precedes the title of the command window. To continue, press the space bar or Escape.

3. Select OK.

   NOTE:  (Development upgrades only.) At this point, the mainframe-centric upgrade defaults to the midtier-centric approach to the upgrade. That is, differences between the two types of development upgrade exist only for the upgrep phase and only for the steps before this step. When you restart the upgrep process on the midtier after the third pause, the same sequence of steps are run for both mainframe-centric and midtier-centric development upgrades.