Preparing to Run the Siebel Database Configuration Wizard

Environments: Development, Test and Production.

Use this topic to identify the information you must enter when running the Database Configuration Utilities. Collect this information, and verify that it is correct before running the utilities.

Note: If you are running Siebel CRM version 8.1.1 (SEA), and want to migrate to Siebel CRM version 8.1.1 (SIA), then you do so with the Database Configuration Wizard.

The Database Configuration Utilities are a group of wizards that request information about the upgrade process you want to perform. The utilities add this information to a primary upgrade configuration file and call an SQL generator. The SQL generator uses the information to create or populate SQL files:

The following table lists the information that the utilities request for performing an upgrade.
The table on the following page lists the additional information specific to Additive Schema Changes mode.

After the Database Configuration Wizard exits you run the Upgrade Wizard. The Upgrade Wizard executes the SQL files against the Siebel database.

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 Server (Siebel Database Configuration Utilities) is installed. For example: `C:\sba81\dbsrvr`.
RDBMS Platform	Choose the RDBMS type: IBM DB2, Microsoft SQL Server, or Oracle Database. Note: For IBM DB2 for z/OS, see Siebel Database Upgrade Guide for DB2 for z/OS instead of this guide.
Siebel Database Operation menu	For upgrep, upgphys and Prepare for Production modes, choose Upgrade Database. For Apply Additive Schema Changes mode, choose Apply Additive Schema Changes. The remaining menu choices are for database installation and administration.
Environment Type	Choose Development for development environment upgrades. Choose Production for test environment and production environment upgrades.
Upgrade Options	Choose one of the following: Development Environment: Upgrade Siebel Database Schema (upgrep) Upgrade Custom Database Schema (upgphys) Production Environment: Upgrade Siebel Database Schema (upgrep and upgphys)
Siebel Industry Application	As appropriate for the environment you are upgrading from, choose SIA (for Siebel Industry Applications) or SEA (for Siebel Business Applications, also known as Siebel Cross-Industry Applications).
Current Siebel Version	Choose the option for the application version that you are upgrading your Siebel database from. For more information about valid options for performing a full database upgrade, see Supported Upgrade Paths for Siebel CRM. For information about specifying options for performing an Incremental Repository Merge instead, see Performing a Siebel Incremental Repository Merge.
Database Encoding	Indicate whether your database uses a Unicode code page.
ODBC Data Source Name	Verify the ODBC name for connecting to the Siebel database that you are upgrading. If the ODBC name is not correct, then enter the correct name.
Database User Name and Database Password	Account name and password for the Siebel administrator of the Siebel database that you are upgrading. Note: For more information about supported characters for Siebel passwords, see Siebel Security Guide.
Database Table Owner and Database Table Owner Password	Account name and password for the Siebel database table owner. Note: For more information about supported characters for Siebel passwords, see Siebel Security Guide.
Index Table Space Name and Table Space Name	Oracle Database and IBM DB2 only. Index tablespace name and tablespace name (4-KB tablespace name for IBM DB2).
16-KB Table Space Name, 32K Table Space Name	IBM DB2 only. The 16-KB and 32-KB tablespace names.
Database Server OS	Choose the RDBMS server operating system type.
Parallel Indexing	Oracle Database only. Select parallel indexing if you want SQL commands for index creation to include the arguments parallel and no logging. Parallel indexing causes an index to be created using parallel processing, which requires an RDBMS server with multiple processors. Verify with your database administrator whether your RDBMS server is configured for parallel processing. Tip: Oracle Library search phrase: parallel execution. Selecting parallel indexing does not cause multiple indexes to be created simultaneously, in parallel. To set up parallel indexing, you must set up parallel index-creation threads using Siebel Upgrade Tuner. You create parallel threads as part of tuning the production upgrade files. For more information, see Tuning the Siebel Upgrade Files
Security Group ID/Grantee	Security group or grantee name for Siebel application users. Must have select, update, insert, and delete privileges on Siebel application tables. Specify SSE_ROLE.
Custom Scripts Directory	During the upgrade process, the Repository Sanitization script is executed. This script scans the prior customer repository to check if there are any unreferenced repository objects across multiple applications. The unused objects are then inactivated. If a repository object is referred to in a custom script, it will not be a candidate for inactivation. Custom files have to be copied from the following locations: For Siebel CRM 15.0 and prior releases: `<SWSE HOME>\public\<LANG>\<BUILD#>\scripts\siebel\custom` For Siebel CRM 16.x: `<SWSE HOME>\public\scripts\<LANG>/siebel/custom` In addition, copy every language required into a directory and specify that location.
Web Templates Directory	Directory where the custom web templates are stored. From Siebel CRM 17.0 onwards, web templates are stored in the database. Since custom web templates must be moved to the database as well, a step is executed during the upgrade process that moves all the web templates specified in this particular location to the database. You must copy over the custom files from previous releases from: `<SES>\siebsrvr\webtempl` Copy all the custom files into a single directory and then specify that location in the upgrade path when prompted.
Verify Repository After Upgrade	Indicate whether you want to execute the steps to verify the repository during upgphys. To perform upgphys separately, select the Verify Repository After Upgrade option in the Database Configuration Wizard.
Upgrep log directory	If you select the option Verify Repository After Upgrade in the previous step, then you will have to provide the log directory of the upgrep process. The log directory is of the form: `$SIEBEL_ROOT/siebsrvr/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	Specify a different subdirectory, under the `log` directory, in which to create the log files. Accept the default or enter the directory name. If the directory does not exist, then it will be created. Do not use special characters, such as spaces or slashes.
Select runupg option	Indicate whether you want to run the operation you configured or run it at another time.