Siebel Anywhere Administration Guide > Defining Upgrade Kits >

Defining a Siebel Database Schema Upgrade Kit


This topic provides specific instructions for defining a Siebel Database Schema upgrade kit using the Upgrade Kit Wizard.

Installing a Siebel Database Schema upgrade kit synchronizes the logical and physical schemas on the Mobile Web Client and regional databases.

CAUTION:  In an IBM DB2 environment, before creating Siebel Database Schema upgrade kits, you must drop all customized views and triggers. Otherwise, the upgrade kit will fail.

To define a Siebel Database Schema upgrade kit

  1. Gather the information you will need, as described in Planning and Preparing to Use Siebel Anywhere.
  2. Start the Upgrade Kit Wizard, as described in Running the Upgrade Kit Wizard.
  3. Use the information you have gathered and the information in Table 17 to respond to the prompts in the Upgrade Kit Wizard.
  4. When you have finished specifying data about the upgrade kit you are defining, click Finish to pass the request to the Upgrade Kit Builder server component and to exit from the Upgrade Kit Wizard.

    A new row for the new upgrade kit appears in the Upgrade Kits list, with Status set to Request Submitted. For more information about the upgrade kit information available in this list and other lists, see Viewing Upgrade Kit Properties.

    After you define your upgrade kit, you must proceed to activate, apply, and distribute it. For more information about these tasks, see Activating, Applying, and Distributing Upgrade Kits.

    NOTE:  Be sure to check the log file after Upgrade Kit Builder creates a Siebel Database Schema upgrade kit. Make sure that error messages or warnings, if any, are nonfatal.

The information in Table 17 is presented in approximately the sequence used by the Upgrade Kit Wizard.

Table 17. Upgrade Kit Wizard Elements for a Siebel Database Schema Upgrade Kit
Wizard Element
Element Type
Comments

Upgrade Component

Drop-down list

The name of the component the upgrade kit will install or upgrade. Select Siebel Database Schema.

ODBC Data Source

Text field

The name of the ODBC data source used to connect to the HQ database.

User Name

Text field

The Siebel administrator login ID used to connect to the database.

User Password

Text field

The Siebel administrator password used to connect to the database.

Schema Qualifier

Text field

(IBM DB2 for z/OS only) the name used to qualify all database objects created that are required by Siebel Business Applications.

Privileged User ID

Text field

Required. The user account that has the necessary database authority and privileges to perform operations required to implement Siebel Business Applications, including creating, accessing, and modifying Siebel database objects and native database objects. These environments have rigid controls on user identification: accounts must correspond to a real person. For a database other than IBM DB2 for z/OS, this account is the same account as table owner.

Privileged User Password

Text field

The Privileged User's password on the Regional Database. For a database other than IBM DB2 for z/OS, this password is the table owner's password.

Table Space

Text field

(Oracle Database or IBM DB2 only) The database tablespace or segment for Siebel tables. Tablespaces are created during initial installation or by the DBA. Obtain this value from your DBA or through a SQL query on the server database.

Index Space

Text field

(Oracle Database or IBM DB2 only) The database tablespace or segment for Siebel indexes. Obtain this value from your DBA through a SQL query on the server database.

16K Table Space

Text field

(IBM DB2 only) Obtain the optional parameter from your DBA or through a SQL query on the server database.

32K Table Space

Text field

(IBM DB2 only) Obtain the optional parameter from your DBA or through a SQL query on the server database.

Table Group File

Text field

(IBM DB2 for z/OS only) Obtain the optional parameter from your DBA or through a SQL query on the server database.

Minimum Old Version

Read-only text field

The earliest component version that can download and install the upgrade kit. This setting is automatically set to NULL for history-independent component types, including Siebel Database Schema, indicating that there are no prerequisite versions required for using the upgrade kit. For more information about choosing version values, see Determining Version-Setting Values.

Maximum Old Version

Read-only text field

The latest component version that can download and install the upgrade kit. This setting is automatically set to NULL for history-independent component types, including Siebel Database Schema, indicating that there are no prerequisite versions required for using the upgrade kit. For more information about choosing version values, see Determining Version-Setting Values.

New Version

Text field

The version number that the component being upgraded will have after the upgrade kit is installed. The default value is 1 greater than the current version for the component to be upgraded. For more information about choosing version values, see Determining Version-Setting Values.

Activate Upgrade Kit

Check box

When this check box is selected, the data to be included in the upgrade kit will be compressed into a single archive on the Siebel File System automatically. You can also perform activation manually, as described in Activating, Applying, and Distributing Upgrade Kits.

For most upgrade kits, it is recommended that you select this check box. However, if you are creating an upgrade kit that is dependent on another upgrade kit, then clear this check box. For more information about working with dependent upgrade kits, see Controlling the Order of Upgrade Kit Installation.

Apply Versions

Check box

This check box is displayed only if you previously selected the Activate Upgrade Kit check box in the Upgrade Kit Wizard.

When this check box is selected, the compiled information string in the database will be updated automatically with the component version information for this upgrade kit. You can also apply versions manually, as described in Activating, Applying, and Distributing Upgrade Kits.

For most upgrade kits, it is recommended that you select this check box. However, if you are creating an upgrade kit that is dependent on another upgrade kit, then clear this check box. For more information about working with dependent upgrade kits, see Controlling the Order of Upgrade Kit Installation.

Required Upgrade Kit

Check box

This check box is displayed only if you previously selected the Apply Versions check box in the Upgrade Kit Wizard.

When this check box is selected, the upgrade kit will be required regardless of the previous versions installed. (Min Version and Max Version are set to the value of New Version, but this change is not visible in the Upgrade Kit Wizard.)

Make Siebel Database Schema upgrade kits required when they are distributed to users in a production environment. However, it is recommended that you create and test the upgrade kit as an optional upgrade kit before making it required. For more information about changing an optional upgrade kit to be required, see Converting an Optional Upgrade Kit to a Required Upgrade Kit.

Upgrade Kit Title

Text field

An identifier for the upgrade kit. The default value is the value of Upgrade Component Name followed by a space and the value of New Version. However, you can modify the title while defining the upgrade kit. After the upgrade kit is defined, this identifier appears in the Name field of the Upgrade Kits list.

Comments

Text field

This field is available for comments about the upgrade kit. Comments entered here are displayed in the Upgrade Kits list.

NOTE:  To avoid unnecessary download operations, it is recommended that you keep only one upgrade kit for history-independent components, including Siebel Database Schema upgrade kits. Depending on your preference, you can either delete or deactivate previous upgrade kits for a history-independent component. Deleting an upgrade kit increases available space in the Siebel File System. Deactivating an upgrade kit prevents use of the upgrade kit, while keeping it available in case you need it unexpectedly.

For detailed information about using a Siebel Database Schema upgrade kit, see Process of Updating the Siebel Database Schema.

Siebel Anywhere Administration Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.