Bookshelf v7.8: Preparing to Run the Siebel Database Server Configuration Utilities

Use this topic to identify the information you must enter when running the Database Server Configuration Utilities. Collect this information and verify it before running the utility.

The Database Server Configuration Utilities requests information about the upgrade process you want to perform. It then adds this information to a master upgrade file and calls an SQL generator. The SQL generator uses the information to create or populate SQL files.

The Upgrade Wizard runs after the Database Server Configuration Utilities exits. The wizard executes the SQL files against the Siebel Database.

Under Windows, the Database Server Configuration Utilities is a wizard that displays a series of windows. You enter the requested information in each window. Most of the windows contain a help button. When you click Help, an explanation of what to enter in the wizard displays.

Under UNIX, the Database Server Configuration Utilities displays as a set of screens in a shell command window. You enter the requested information at the prompt.

Table 31 lists the information that you must enter in the Database Server Configuration Utilities.

Table 32 lists additional information the utility requires when you perform a production environment or production upgrade.

Table 31. Information Required for the Database Server Configuration Utilities
Screen Name	Required Information
Gateway Name Server Address	Windows only. The Siebel Gateway Name Server machine name and the Enterprise Server name.
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 is installed—for example: `C:\sea7xx\dbsrvr.`
RDBMS Platform	Choose the RDBMS type.
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 test environment and production environment upgrades.
Upgrade Options	Choose the upgrade mode, for example Prepare for Production upgrade or upgrep.
Siebel Industry Application	This displays if you are upgrading from a Siebel Industry Solution or Siebel Industry Application. Choose the application you are upgrading from. If you have upgraded to the base Siebel Business Application as part of upgrading to the new Siebel Industry Application release, choose Siebel Horizontal Application.
Current Siebel Version	Choose the application version you are upgrading from.
Database Encoding	Indicate whether your database uses a Unicode code page.
Language Selection	Upgrades with more than one language pack installed only. Choose the primary (base) language that is installed. The primary language is the language in which the data is stored in the Siebel Database that is being upgraded.
ODBC Data Source Name	Verify the ODBC name for connecting to the Siebel Database you are upgrading. If it is not correct, enter the correct ODBC name.
Database User Name	Account name and password for the Siebel Administrator of the Siebel Database you are upgrading.
Database Table Owner	Account name and password for the Siebel Database table owner.
Index Table Space Name	Oracle and IBM DB2 only. Index tablespace name and tablespace name (4-KB table's space name for DB2).
16-KB Table Space Name	DB2 only. The 16-KB and 32-KB tablespace names.
Database Server OS	Choose the RDBMS server operating system type.
Parallel Indexing	Oracle only. Select parallel indexing if you want SQL commands for index creation to include the arguments parallel, no logging. This causes an index to be created using parallel processing. This requires an RDBMS server with multiple CPUs. See your DBA to confirm if 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 do this, you must set up parallel index-creation threads using Siebel Upgrade Tuner. You create parallel threads as part of tuning the production upgrade files. See Tuning the Siebel Upgrade Files.
Log Output Directory	Accept the default or enter the directory name. If the directory does not exist, it will be created. Do not use special characters such as spaces or slashes.

Additional Information Required for Production Upgrades

When you perform a production test environment or production environment upgrade, the additional information shown in Table 32 is required when you run the Database Server Configuration Utilities in Prepare for Production mode.

Note that several screens request information about the Siebel Database in the development environment, not the production test or production environment.

Table 32. Additional Information Required for Production Upgrades
Screen Name	Required Information
ODBC Data Source Name for Development Database	The ODBC name for connecting to the development environment Siebel Database. If you are upgrading without a development environment, this is the ODBC name of the reference database.
Database User Name for Development Database	Account name and password of the Siebel Administrator of the Siebel Database in the development environment.
Database Table Owner for Development Database	Account name and password for the Siebel Database table owner in the development environment.
Repository Name for Development Database	Enter the name of the upgraded Siebel Tools repository in the development environment database. Typically, this is Siebel Repository.

Upgrade Guide		Copyright © 2006, Oracle. All rights reserved.