1. Anywhere Administration Guide
  2. Process of Updating the Siebel Database Schema

Process of Updating the Siebel Database Schema

This topic describes the overall process of using Siebel Anywhere to update the Siebel database schema. Typical schema changes include:

  • Adding extension columns to Siebel base tables

  • Adding extension tables to the Siebel database

  • Creating or modifying indexes

To update the Siebel database schema, perform the following tasks:

  1. Review the information presented in Review What Happens During a Siebel Database Schema Upgrade.

  2. Make and test the Siebel database schema changes in the development environment, using Siebel Tools. For more information about this step, see Changing the Siebel Database Schema in a Development Environment.

  3. Move the schema changes to the test environment, using the Siebel Database Configuration Wizard. For more information about this step, see Moving Siebel Database Schema Changes Between Environments.

  4. Create the necessary upgrade kits in the test environment. For more information about this step, see Creating Upgrade Kits for Siebel Database Schema Changes.

  5. Prepare the test Mobile Web Clients and Regional Node Servers for the schema changes. For more information about this step, see the following topics:
  6. Install the schema changes on the test Mobile Web Clients and Regional Node Servers. For more information about this step, see the following topics:

  7. Move the schema changes to the production environment, using the Siebel Database Configuration Wizard. For more information about this step, see Moving Siebel Database Schema Changes Between Environments.

  8. Create the necessary upgrade kits in the production environment. For more information about this step, see Creating Upgrade Kits for Siebel Database Schema Changes.

  9. Prepare the production Mobile Web Clients and Regional Node Servers for the schema changes. For more information about this step, see the following topics:
  10. Install the schema changes on the production Mobile Web Clients and Regional Node Servers. For more information about this step, see the following topics: