|
Siebel Anywhere Administration Guide > Defining Upgrade Kits >
Defining a Siebel Database Schema Upgrade Kit
This section provides specific instructions for defining a Siebel Database Schema upgrade kit using the Upgrade Kit Wizard. Installing the schema upgrade kit synchronizes the logical and physical schemas on Mobile Web Client and Regional Node Server databases. CAUTION: In the DB2 environment before creating 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
- Gather the information you will need, as described in Upgrade Planning and Preliminary Tasks.
- Start the Upgrade Kit Wizard using the instructions in Running the Upgrade Kit Wizard.
- Use the information you have gathered and the information in Table 18 to respond to the prompts in the Upgrade Kit Wizard.
- When you have finished specifying data about the upgrade kit you are defining, click Finish to pass the request to the Upgrade Kit Builder 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 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 information on these tasks, see Activating, Applying, and Distributing Upgrade Kits.
NOTE: Be sure to check the log file after Upgrade Kit Builder creates a database schema kit—make sure that error messages or warnings, if any, are nonfatal.
Information in Table 18 is presented in approximately the sequence used by the Upgrade Kit Wizard.
Table 18. Upgrade Kit Wizard Elements for a Siebel Database Schema Upgrade Kit
|
|
|
Upgrade Component |
Drop-down list |
Name of the component the upgrade kit will install or upgrade. Select Siebel Database Schema. |
ODBC Data Source |
Text field |
Name of the ODBC data source used to connect to the HQ database. |
User Name |
Text field |
Siebel administrator login ID used to connect to the database. |
User Password |
Text field |
Siebel administrator password used to connect to the database. |
Schema Qualifier |
Text field |
For DB2/390 and AS/400 environments only, the name used to qualify all database objects created that are required by Siebel eBusiness Applications. |
Privileged User ID |
Text field |
Required. User account that has the necessary database authority and privileges to perform operations required to implement Siebel, 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 DB2/390 or AS/400, this account is the same account as table owner. |
Privileged User Password |
Text field |
Privileged User's password on the Regional Database. For a database other than DB2/390 or AS/400, this password is the table owner's password. |
Table Space |
Text field |
Database table space or segment for Siebel tables. Table spaces are created during initial installation or by the DBA. Obtain this value from your DBA or through a SQL query on the server database. Not required for Oracle or MSSQL. |
Index Space |
Text field |
Database table space or segment for Siebel indexes. Obtain this value from your DBA through a SQL query on the server database. Not required for Oracle or MSSQL. |
16K Table Space |
Text field |
Obtain the optional parameter from your DBA or through a SQL query on the server database. This setting is specific to the DB2 database platform. |
32K Table Space |
Text field |
Obtain the optional parameter from your DBA or through a SQL query on the server database. This setting is specific to the DB2 database platform. |
Table Group File |
Text field |
Obtain the optional parameter from your DBA or through a SQL query on the server database. This setting is specific to the DB2/390 database platform. |
Minimum Old Version |
Read-only text field |
Earliest component version that can download and install the upgrade kit. Automatically set to NULL for history-independent component types, including database schemas, indicating that there are no prerequisite versions required for using the kit. For more information about choosing version values, see Determining Version Setting Values. |
Maximum Old Version |
Read-only text field |
Latest component version that can download and install the upgrade kit. Automatically set to NULL for history-independent component types, including database schemas, indicating that there are no prerequisite versions required for using the kit. For more information about choosing version values, see Determining Version Setting Values. |
New Version |
Text field |
Version number that the component being upgraded will have after the upgrade kit is installed. 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 information to be included in the upgrade kit will be compressed into a single archive on the Siebel File System automatically. Activation can also be performed 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 dependant on another upgrade kit, be sure to clear this check box. For information about working with dependent kits, see Controlling the Order of Kit Installation. |
Apply Versions |
Check box |
Displayed only if Activate Upgrade Kit check box was selected in an earlier Upgrade Kit Wizard screen. 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. Applying versions can also be performed 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 dependant on another upgrade kit, be sure to clear this check box. For information about working with dependent kits, see Controlling the Order of Kit Installation. |
Required Upgrade Kit |
Check box |
When this check box is selected, the upgrade kit will be required regardless of previous versions installed. (Min Version and Max Version are set equal to New Version, but this change is not visible in the Upgrade Kit Wizard.) Displayed only if Apply Versions check box was selected in an earlier Upgrade Kit Wizard screen. Database Schema upgrade kits should be required kits when they are distributed to users in a production environment. However, it is recommended that you create and test the kit as an optional kit before making it required. For information about changing an optional kit to a required kit, see Converting an Optional Kit to a Required Kit. |
Upgrade Kit Title |
Text field |
Identifier for the upgrade kit. Defaults to Upgrade Component Name value followed by a space and the New Version value, but can be modified during the kit definition process. After the kit is defined, this identifier appears in the Name field of the Upgrade Kits list. |
Comments |
Text field |
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 database schema kits. Depending on your preference, you can either delete or inactivate previous kits for a history-independent component. Deleting a kit increases available space in the Siebel File System. Inactivating a kit prevents use of the kit, while keeping it available in case you need it unexpectedly.
For detailed information about using a database schema upgrade kit, see Performing Database Schema Updates.
|
