|
Siebel Database Upgrade Guide > Upgrading the Siebel Database >
Preparing to Run the Siebel Database Configuration Wizard
Upgrades from: All Supported Siebel releases. Environments: Development, production test, production. Databases: All databases. This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade. 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. The Database Configuration Utilities are a group of wizards that request information about the upgrade process you want to perform. They add this information to a master upgrade file and call an SQL generator. The SQL generator uses the information to create or populate SQL files:
- Table 29 lists the information that the utilities request for performing an upgrade.
- Table 30 lists the additional information specific to Prepare for Production mode.
- Table 31 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.
Table 29. Information Required for the Database Configuration Utilities
|
|
Gateway Name Server Address |
The Siebel Gateway Name Server machine name. |
Enterprise Server Name |
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:\sba80\dbsrvr. |
RDBMS Platform |
Choose the RDBMS type. |
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 production 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:
- Prepare for production
- Upgrade Siebel Database Schema (upgrep and upgphys)
|
Siebel Industry Application |
Choose the industry 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 and Database Password |
Account name and password for the Siebel administrator of the Siebel Database you are upgrading. |
Database Table Owner and Database Table Owner Password |
Account name and password for the Siebel Database table owner. |
Index Table Space Name and Table Space Name |
Oracle and IBM DB2 only. Index table space name and table space name (4-KB table space name for 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 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. |
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. Default is SSE_ROLE. |
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 Prepare for Production Mode
NOTE: This topic is only applicable for upgrades from Siebel Business Applications release 7.5.3 to version 8.1. If, for example, you are upgrading from version 7.7 to 8.0, you need not perform this step.
Before performing the production upgrep and upgphys, you must run the Database Server Configuration Utilities in Prepare for Production Mode. The additional information shown in Table 30 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 30. Additional Information Required for Prepare for Production Mode
|
|
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. |
Additional Information Required for Apply Additive Schema Changes Mode
You can optionally run the Database Configuration Utilities in Apply Additive Schema Changes mode. Additive Schema Changes generates an SQL script, schema.additive.sql. The script contains production upgrep schema changes that can be performed while the database is online. This reduces the amount of time required for the upgrep when the database is offline. The additional information shown in Table 31 is required when you run the Database Configuration Utilities in Apply Additive Schema Changes mode.
Table 31. Additional Information Required for Apply Additive Schema Changes Mode
|
|
Schema File |
The absolute path to the schema.ddl file. If a path is displayed, verify that schema.ddl is located in this directory. |
Output Directory |
The absolute path to the directory where schema.additive.sql will be placed after the Upgrade Wizard generates it. The Upgrade Wizard also places the log file in this directory. |
Related Topics
About the Siebel Database Configuration Utilities.
About Siebel Additive Schema Changes Mode
| 
