Information Required by the Database Configuration Wizard

Upgrades: All upgrades.

Environments: All environments

This topic is part of an upgrade process. See Performing a Siebel Database Upgrade.

Use this topic to identify the information you must enter when running the Database Configuration Wizard. Make sure you have prepared your upgrade environment, and have collected and verified this information before running the wizard.

The Database Configuration Wizard requests information about the upgrade process you want to perform. It then adds this information to a primary upgrade configuration file. The Siebel Upgrade Wizard runs after the Database Configuration Wizard exits. The wizard generates the upgrade SQL files and executes some of the SQL files against the Siebel database. For more information on the Database Configuration Wizard, see About the Siebel Database Configuration Utilities and Database Configuration Wizard.

The following table lists the information that you must enter in the Database Configuration Wizard when performing the upgrade processes. The table on the following page lists additional information the utility requires when you perform a production environment upgrade.

Field Name or Menu	Required Information
Siebel Server Directory	The absolute path of the directory where the Siebel Server is installed. For UNIX, do not enter the string `$SIEBEL_ROOT`.
Siebel Database Server Directory	The absolute path of the directory where the Siebel Database Configuration Utilities are installed, for example `C:\sba81\dbsrvr` (Windows) or `siebel/dbsrvr` (UNIX).
RDBMS Platform	Choose IBM DB2 UDB for z/OS.
Siebel Database Operation	Choose Upgrade Database. The other menu choices are for database installation and administration.
Environment Type	Choose Development for development environment upgrades. Choose Production for production and production test environment upgrades.
Upgrade Options	Choose one of the following options: Development environments: Upgrade Siebel Database Schema (upgrep) Upgrade Custom Database Schema (upgphys) Production Environments: Prepare for Production Upgrade Upgrade Siebel Database Schema (upgrep + upgphys)
Upgrade Process	If you chose the Upgrade Siebel Database Schema option for either a production or development environment, select one of the following: zSeries Staging of Files for Upgrade: to create the staging database DDL and to generate upgrade files zSeries Seed/Repository Upgrade: to automatically populate and upgrade data on the database
Siebel Industry Application	Choose the application you are upgrading from. If you have upgraded to the base Siebel Business Applications as part of upgrading to the new Siebel Industry Applications release, choose Siebel Horizontal Application.
Current Siebel Version	Choose the application version you are upgrading from. If you are upgrading within the same Siebel release, choose the application version you are upgrading from based on the following criteria: If your Siebel database is currently on version 8.1.1.14, then choose v8_1_1_14. Choose this option if you migrated your Siebel CRM software from version 8.1.1.14. Choose option v8_1_1SIA_To_v8_1_1_9SIA under the following conditions: If you are currently on Siebel CRM version 8.1.1.0 to 8.1.1.9 (SIA) and migrating to Siebel 2020 or later (SIA). If you have installed Siebel SIA 8.1.1.10 binaries only, and have not previously executed incremental repository merge, and are migrating to Siebel 2020 or later. Choose option v8_1_1_10 under the following conditions: If you have installed Siebel SIA 8.1.1.10 binaries, but have also previously executed incremental repository merge, and are migrating to Siebel 2020 or later. If you have performed a new installation of Siebel CRM version 8.1.1.10 (SIA) including database installation previously and are migrating to Siebel 2020 or later. Choose option v8_1_1_11 under the following conditions: If you are currently on Siebel CRM version 8.1.1.11 (SIA) and are migrating to Siebel 2020 or later.
Siebel Tools Installation Directory Siebel Tools Data Source (Specify both values for Incremental Repository Merge on Windows)	Siebel Tools Installation Directory $SIEBEL_HOME\. The directory where Siebel Tools is installed such as `c:\Siebel\Tools`. This entry applies only to the Siebel Server installed on Windows. Siebel Tools Data Source. Provide the data source name that you use to log in using Siebel Tools, such as ServerDataSrc. This entry is in `$SIEBEL_HOME\BIN\Language\tools.cfg`.
Database Encoding	Indicate whether your database uses an ASCII or EBCDIC code page.
Host/LPAR name where Target database resides DB2 Subsystem name of Target database.	Host/LPAR name where Target database resides: The name of the host or LPAR where the target database is located. You can either specify the same or different Host/LPAR names for the target and staging databases. DB2 Subsystem name of Target database: The DB2 subsystem name of the target database. You must specify a different DB2 subsystem name for the target and staging databases.
Schema/Tableowner qualifier name on Target database	Enter the up to eight-character identifier that designates the Siebel schema for your target database. This is also an authorization ID. The schema qualifier must start with a letter, cannot contain special characters, and must be entered in uppercase. The target database tableowner name can be the same or different to the staging database tableowner name.
ODBC Data Source Name of Target database	Verify the ODBC name for connecting to the target Siebel database. The default value of the target database ODBC DSN is the DB2 subsystem name. When you set up the ODBC connection in DB2 Connect, you can use the actual subsystem name for the database alias. Note: To find the name of your ODBC data source, navigate to the Start menu, then select Settings, Control Panel, and then ODBC data source. Click the System DSN tab and you will find the name of your ODBC data source. To find the name of your ODBC data source on UNIX, type: `vi $ODBCINI`.
Valid/Authorized Target database user name or group name	Enter the target database user name for the Siebel administrator of the target database. For further information on the database user name, see Granting a Siebel User Upgrade Authorization.
Valid/Authorized Target database password	Enter the password associated with the username of the Siebel administrator of the target database.
Host/LPAR name where the Staging database resides	The host or LPAR name of the staging database. The staging and target Host/LPAR names can be the same or different.
DB2 Subsystem name where the Staging database resides	The DB2 subsystem name of the staging database. You must specifydifferent DB2 subsystem names for the target and staging databases.
Schema/Tableowner qualifier name for Staging database	Enter the up to eight-character identifier that designates the Siebel schema for your staging database. This is also an authorization ID. The schema qualifier must start with a letter, cannot contain special characters, and must be entered in uppercase. The staging database tableowner name can be the same or different to the target database tableowner name.
Authorized TSO account ID used to connect and FTP files to Enterprise Server(s)	Enter your TSO account ID. This account ID must have the authorization to allocate and create data sets on the z/OS host.
Dataset High-level Qualifier for all Host (Staging and Target) dataset names	Specify the high-level qualifier you want to use for the z/OS upgrade data sets. Follow your organization’s naming standards.
Security Group ID / Grantee.	Enter the user ID of the group to whom schema access is granted, for example, `SSEROLE`.
Storage Group for Temporary Indexes	Enter the name of the storage group provided by the database administrator for the staging database (the default value is `SYSDEFLT`). The staging database storage group name can be the same or different to the target database storage group name
Storage Control File	Enter the path and name of the storage control file you want to use as follows: zSeries Staging of Files for Upgrade: When you select this upgrade process, specify the storage control file of the target database. zSeries Seed/Repository Upgrade: When you select this upgrade process, specify the storage control file that contains the previously customized database storage layout (this is the file you prepared in Process of Preparing the Storage Layout of the Schema).
Primary Quantity for Temporary Index Space	Enter the minimum amounts of primary index space allocated for temporary indexes generated during the upgrade.
Secondary Quantity for Temporary Index Space	Enter the minimum amounts of secondary index space allocated for temporary indexes generated during the upgrade.
DDL Commit Frequency	Enter the DDL commit frequency for your upgrade.
Output Directory	Accept the default output directory name or enter a new directory name. Note: When the upgrade process is complete, this directory contains all of the files necessary to create the staging database or run the upgrade. These files must be manually applied by the database administrator.
Verify Repository after upgrade	Indicate whether you want to execute Verify Repository steps during upgphys. To perform upgphys separately, select the Verify Repository after Upgrade option in the database server configuration.
Upgrep log directory	If you select the Verify Repository After Upgrade option, enter the log directory of the upgrep process. The log directory is of the form `SIEBEL_ROOT/log/upgrep_dev_UpgradeNumber.` For example: `C:/ses/siebsrvr/log/upgrep_dev_811`. The log directory path is a requirement for generating the seed data conflict report.
Log Output Directory	Accept the default output directory for upgrade log files name or enter a new directory name.
Select runupg option	Indicate whether you want to run the operation that you configured or run it at another time.