Upgrade Guide for DB2 UDB for z/OS > Preparing a Production Environment for Upgrade >

Prerequisites for a Production Upgrade

Upgrades: All upgrades.

Environments: Production test, production.

NOTE:  You must be thoroughly familiar with the upgrade process before beginning the production upgrade. Before upgrading your production environment, perform a test upgrade in your production test environment to familiarize yourself with the process and to eliminate errors that can affect upgrade success or performance.

Before beginning the upgrade of your production environment, verify that the production database configuration meets the database requirements outlined in the section Verifying Database Server Configuration.

NOTE:  Verify that your production database uses binary sort order.

About Subsystems and Tableowners

Table 21 describes the subsystem and tableowner requirements for the production upgrade.

If you have not already done so, copy the Upgrade Planning Worksheet, located in Upgrade Planning Worksheet and fill out the appropriate fields with the following information. Contact your database administrator or systems programmer for help in completing the worksheet. Also, refer to Preparing to Run the Database Server Configuration Utility for a description of the information you are required to enter when you run the Database Server Configuration Utility to perform upgrade operations.

Source Database Values

For the production environment upgrade, you need the following values for your source database:

• ODBC Data Source Name. This name must be the same as the name of the database qualifier.

  NOTE:  On Microsoft Windows, the Siebel Server installation process automatically creates the data source, using the format SiebSrvr_EnterpriseName. 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.

• Database User Name. The ID allowed to log into the Siebel Database. This user ID should have authorization to set CURRENT SQLID and must be set up as an employee within your Siebel Business application. The employee record must have the Siebel administrator responsibility. SADMIN is the default administrator user name and password, but you can use any name that has SADMIN credentials. If this user does not already exist in your database, or does not have Siebel administrator privileges, then you must add this to your database prior to proceeding with the upgrade. For more information, see Adding a Siebel User.

  This login must be the same as the target database user name that you will specify in the upgrade configuration utility.

• Database Password. The password for the ID used to log into the Siebel Database.
• Schema Qualifier. The up to eight-character identifier that designates Siebel Schema. This is also an authorization ID. The schema qualifier must start with a letter, cannot contain special characters, and must be entered in uppercase.
• Group Authorization ID. The user ID of the group to whom schema access is granted, for example, SSEROLE.

Target Database Values

For the production environment upgrade, you need the following values for your target database:

• Schema Qualifier. The up to eight-character identifier that designates Siebel Schema. This is also an authorization ID. The schema qualifier must start with a letter, cannot contain special characters, and must be entered in uppercase.
• DB2 Subsystem. Verify that there are no objects in the target DB2 subsystem before you start the upgrade.
• Database User Name. The ID allowed to log into the Siebel Database, for example, SBLDBA. This user ID should have authorization to set CURRENT SQLID and must be set up as an employee within your Siebel Business application. The employee record must have the Siebel administrator responsibility. SADMIN is the default administrator user name and password, but you can use any name that has SADMIN credentials. If this user does not already exist in your database, or does not have Siebel administrator privileges, then you must add this to your database prior to proceeding with the upgrade. For more information, see Adding a Siebel User.

  This login must be the same as the target database user name that you will specify in the upgrade configuration utility.

• Database Password. The password for the ID used to log into the Siebel Database.
• Group Authorization ID. The user ID of the group to whom schema access is granted, for example, SSEROLE.
• Storage Group for Indexes. The name of the storage group used for temporary indexes. The default value is SYSDEFLT.
• Storage Group for Tables. The name of the storage group used for temporary tables. The default value is SYSDEFLT.
• ODBC Data Source Name. This name must be the same as the name of the database qualifier.

The remaining information required for upgrade will be derived from your prior source database layout.