Siebel Anywhere Administration Guide > Performing Additional Siebel Anywhere Tasks > Process of Updating the Siebel Database Schema >

Creating Upgrade Kits for Siebel Database Schema Changes

The creation of a Siebel Database Schema upgrade kit has two consequences beyond the creation of the upgrade kit itself:

• Schema changes from the logical schema (in Siebel Tools) are automatically applied to the physical schema of the HQ database.
• The custom schema version number in the HQ database is automatically incremented by one.

This task is a step in Process of Updating the Siebel Database Schema.

The number and type of upgrade kits that you need for deploying Siebel database schema changes depend on the kinds of changes you made to the schema:

• Major schema changes. Siebel Anywhere is suitable for distributing minor Siebel database schema updates that have been created using database extensibility. If you are performing a major upgrade, then do not use Siebel Anywhere to distribute your changes.

  For more information about performing major upgrades, see Siebel Database Upgrade Guide. For more information about extracting database changes for Mobile Web Clients, see Siebel Remote and Replication Manager Administration Guide, and for detailed information regarding database extensibility, see Configuring Siebel Business Applications.

• Incremental schema changes. If your Siebel database schema changes are incremental (that is, if you have added tables, added columns, or changed the names of existing tables or columns), then you can create a Siebel Anywhere upgrade kit to upgrade Mobile Web Clients or a Regional Node Server. You do not need to reextract.
• Preference for reextraction rather than Siebel Anywhere. It is possible to reextract databases for Mobile Web Clients and Regional Databases, rather than updating them using Siebel Anywhere, if you prefer. For more information, see Siebel Remote and Replication Manager Administration Guide.
• Mandatory reextraction for nonincremental schema changes. If your Siebel database schema changes are nonincremental (that is, if you have removed or deactivated tables or columns, which are changes that are not recommended), then you must reextract all Mobile Web Clients and Regional Node Servers. Otherwise, synchronization might fail due to transactions that contain data for columns or tables that are no longer available. Reextraction makes it unnecessary to create a Siebel Database Schema upgrade kit.

After you define the upgrade kit or upgrade kits for your upgrade, you must activate and apply them as described in Activating, Applying, and Distributing Upgrade Kits. If you created both a Siebel Database Schema upgrade kit and a Siebel Repository File upgrade kit, then make sure both are activated and applied before you proceed to the next part of the process.

CAUTION:  If you make any upgrade kits dependent upon the Siebel Database Schema component, then first-time Mobile Web Client users will receive an error when they initialize their local databases. The error will indicate the Siebel Business Applications was unable to check initialization status. This problem does not occur where the local database already exists.