Table 10. Information Required for the Database Configuration Wizard—Upgrade Database
|
|
Gateway Name Server Address Enterprise Server Name |
The Siebel Gateway Name Server machine 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 Configuration Utilities are installed—for example C:\sba80\dbsrvr (Windows) or siebel/dbsrvr (UNIX). |
RDBMS Platform |
Choose IBM DB2 UDB for z/OS. |
Siebel Database Operation menu |
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:
- Upgrade Siebel Database Schema (upgrep): development upgrades only
- Upgrade Custom Database Schema (upgphys): development upgrades only
- Prepare for Production Upgrade: production upgrades only
- Upgrade Siebel Database Schema (upgrep + upgphys): production upgrades only
|
Upgrade Process |
Choose 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 |
This screen appears 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 Business application (HOR). |
Current Siebel Version |
Choose the application version you are upgrading from. |
Database Encoding |
Indicate whether your database uses an ASCII or EBCDIC 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. |
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 where the target database is located. 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 Start > Settings > Control Panel > 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 target database user name and password for the Siebel administrator of the target database. For further information on the database user name, see Granting a Siebel User Upgrade Authorization. |
Host/LPAR name where staging database resides DB2 Subsystem name where staging database resides |
- Host/LPAR name where Staging database resides. The host or LPAR name of the staging or target database. The staging and target Host/LPAR names can be the same or different.
- DB2 Subsystem name where Staging database resides. The DB2 subsystem name of the database. You must specify different 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 datasets 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 datasets. 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 Storage Control File |
Storage Group for Temporary Indexes. Enter the name of the storage group provided by the database administrator (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 Preparing the Storage Layout of the Schema):
|
Primary Quantity for Temporary Index Space |
Enter the primary and secondary quantities for temporary index space. |
DDL Commit Frequency |
Enter the DDL commit frequency for your upgrade. |
Output Directory |
Accept the default or enter the directory name. NOTE: When this 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.
|
