Upgrade Guide for DB2 UDB for z/OS > How the Upgrade Works >

About the Siebel Upgrade Wizard and Driver Files

Upgrades: All upgrades.

Environments: Development, production test, production.

The Siebel Upgrade Wizard makes changes to the Siebel Database using the SQL files and the upgrade configuration file (UCF) generated by the Database Server Configuration Utility. After the Siebel Upgrade Wizard starts, it executes this process:

• Reads the UCF
• Calls a driver
• Passes the information in the UCF to the driver, which then passes UCF file information to:
  • the ddlimp utility, which executes ddl-type SQL commands
  • the dataimp utility, which executes data-related SQL commands

The Siebel Upgrade Wizard also does the following:

• Upgrades Siebel seed data
• Loads the following repositories for development environment upgrades:
  • Prior Standard Repository
  • New Standard Repository
  • New Customer Repository

If ddlimp or dataimp encounter errors, they exit. When the errors have been corrected, you can launch the Siebel Upgrade Wizard, and the upgrade resumes from where it stopped.

Upgrade Wizard Pauses

The Siebel Upgrade Wizard pauses on three occasions during the upgrade process. At each pause, you must transfer the files that the Upgrade Wizard has generated to the z/OS host and execute them before you continue the upgrade. The pauses occur as follows:

1. Launch the Wizard to begin the upgrade and generate PRET files (to Pause #1).
2. Resume the Upgrade Wizard to generate the Data Migration files (to Pause #2).
3. Resume the Upgrade Wizard to generate the Gen Primary and new index files (to Pause #3).
4. Resume the Upgrade Wizard to complete the upgrade process.

The Upgrade Wizard generates separate DDL and DML files:

• Data definition language (DDL) files require database administrator (DBA) privileges and must be applied by a database administrator. The DDL files may be executed from the midtier or from the mainframe, depending on the type of upgrade you are doing.
• Data manipulation language (DML) files do not require DBA privileges. These files are used to create seed data and repository data. These files run automatically after you restart the Upgrade Wizard after Pause 3.

The files generated by the Upgrade Wizard are output by default to the \dbsrvr\db2390\dboutput\upgrade directory or to the DDL Output Directory you specified when you ran the Database Server Configuration Utility.

Driver Files

The Siebel Upgrade Wizard performs the upgrade by executing the commands and SQL scripts contained in driver files. Driver files are in ASCII text format and are organized into steps. Each step specifies which command or SQL script to run.

In a driver file, steps are separated by a blank line, and each step begins with a File Execute Entry number. The key part of each step is the command or script to be executed. When an SQL script is specified, you can review the script and see what changes it will make to the Siebel Database before running the Siebel Upgrade Wizard.

Driver files are provided for each of the major upgrade operations. Examples of development environment upgrade driver files are as follows:

• driver_upgrep_dev_621_mf.ucf
• driver_upgphys_dev_77_mf.ucf

Here is an excerpt from a driver file that controls a development environment upgrep from Release 7.7 SIA to release 7.8 SIA. The excerpt contains three steps:

[Sql File Entry 21]

Type = DbSql

File Name = rename_existing_repositories.sql

Use Table Owner = 1

Use System Admin = 0

IgnoreAllDDLErrors = 0

IgnoreAllDMLErrors = 0

Argument 0 = $SiebelVersion

Title = Verify Repository Name

Title Message Num = 0

Estimated Disk Space = 0

Backup Db = 0

Parallelizable Item = 0

Prompt User For Status = 0

[File Execute Entry 22]

Type = FileExecute

File Name = $SiebelRoot\bin\odbcsql

Check Return Code = 1

Return Code Compliance = 0

16 Bit App = 0

Command Line = /s "$ODBCDataSource" /u $UserName /p $Password /q $DatabaseOwner /separator / /a /c rem /l $SiebelLogDir/delappkey.log $DbsrvrRoot/$DatabasePlatform/delappkey.sql /v

Number of 10 Second Wait Loops = 2000

Return Code = 0

Title = Delete old license key

Title Message Num = 0

Estimated Disk Space = 0

Backup Db = 0

Parallelizable Item = 0

Prompt User For Status = 0

[File Execute Entry 23]

Type = FileExecute

File Name = $SiebelRoot\bin\dataimp

Check Return Code = 1

Return Code Compliance = 0

16 Bit App = 0

Command Line = /u $UserName /p $Password /c "$ODBCDataSource" /d $DatabaseOwner /f $SeedFileName /h Log /w y /q 100 /e n /i $DbsrvrRoot/$Language/$DatabasePlatform/seedupg0.inp /l $SiebelLogDir/seedupg0.log /A 1 /B y

Number of 10 Second Wait Loops = 2000

Return Code = 0

Title = Import Siebel seed data

Title Message Num = 0

Estimated Disk Space = 0

Backup Db = 0

Parallelizable Item = 1

Prompt User For Status = 0

How To Locate Upgrade Driver Files and SQL Scripts

Driver files are stored in the following location:

Windows: DBSRVR_ROOT\DB2390\UPGRADE\VERSION

UNIX: DBSRVR_ROOT/DB2390/UPGRADE/VERSION

where:

VERSION = the version from which you are upgrading, for example V7.7

For example, if you are upgrading from Siebel 7.7, the driver file for the development environment upgrep is as follows:

driver_upgrep_dev_77.ucf

Most of the SQL scripts generated or populated for the upgrade are stored in the same directory as the driver file. The remaining SQL scripts are stored in the \DB2390 directory.

Related Topics

About the Database Server Configuration Utility

About the Repository Merge