Siebel Anywhere Administration Guide > Planning and Preparing to Use Siebel Anywhere > Determining Your Upgrade Requirements >

Other Preliminary Tasks for Upgrade Kits

This topic describes additional preliminary tasks to perform for upgrade kits, based on their specific component types.

This topic is part of Determining Your Upgrade Requirements.

Preliminary Tasks for Siebel Database Schema Upgrade Kits

Perform the following tasks before creating a Siebel Database Schema upgrade kit:

• Make sure that the changes to your Siebel database schema can be distributed by this type of upgrade kit.

  NOTE:  Due to a technical limitation in the Sybase Adaptive Server Anywhere database, you cannot use Siebel Database Schema upgrade kits to add required, non-null extension columns to existing tables in the local database. If you make this kind of database change, then you must deploy it by reextracting your Mobile Web Client users, rather than by using a Siebel Database Schema upgrade kit.

• Make sure the ODBC data source correctly points to the server database that has the modified database definition.
• Determine the values to use for the following settings. For brief descriptions of these settings, see Table 17.
  • User Name (for DBA)
  • User Password (for DBA)
  • Schema Qualifier
  • Privileged User ID
  • Privileged User Password
  • Table Space
  • Index Space
• Use SQL queries on your server database to obtain values for the following parameters, as they apply to your database platform:
  • 16K Table Space
  • 32K Table Space
  • Table Group File
• If you are operating in an IBM DB2 environment, then drop all customized views and triggers before you run the Upgrade Kit Wizard to define a Siebel Database Schema upgrade kit. Otherwise, the attempt to create the upgrade kit will fail.

For more information about the overall process of deploying a Siebel Database Schema upgrade kit, see Process of Updating the Siebel Database Schema.

Preliminary Tasks for Siebel Repository File Upgrade Kits

Perform the following tasks before creating either a Siebel Client Repository File upgrade kit or a Siebel Server Repository File upgrade kit:

• Obtain or create the new repository (SRF) file.
• Place the new repository file in a network location that is accessible to the Siebel Server where the Upgrade Kit Builder is enabled.
• Make a note of the UNC path to the network location where you placed the SRF file.

Preliminary Tasks for Third Party Software Upgrade Kits

Perform the following tasks before creating a Third Party Software upgrade kit:

• Locate or prepare the executable file or script that will be executed on the subscriber's computer when the upgrade kit is installed. Make a note of any input parameters required by the executable file or script for the third-party software.
• Place the executable file in a network location that is accessible to the Siebel Server where the Upgrade Kit Builder is enabled.
• Make a note of the UNC path to the network location where you placed the executable file.
• Determine the location where the third-party software will be installed on the subscriber's computer.

Preliminary Tasks for Siebel Client Customer Revisions Upgrade Kits

Perform the following tasks before creating a Siebel Client Customer Revisions upgrade kit:

• Locate or prepare the executable file or script that will be executed on the subscriber's computer when the upgrade kit is installed. Make a note of any input parameters required by the executable file or script.
• Locate any other files to be included in the upgrade kit, and make a note of the locations where they will be installed on the subscriber's computer.