1. Remote and Replication Manager Administration Guide
  2. Upgrading a Regional Node

Upgrading a Regional Node

You must distribute any object definition modifications that you make to the headquarters, regional, and local databases. This is known as a minor upgrade. Some examples of modifications to object definitions include modifications to the behavior of an application or adding extension columns to a table. You can make these Siebel Repository updates in Siebel Tools and then make sure they are part of the Siebel runtime repository in the regional database or local databases. A set of DDL (Data Definition Language) operations represents schema object modifications.

In any one schema hierarchy, each Replication Manager instance and each remote client must contain the same database schema and Siebel runtime repository. If the Siebel Server and the remote client do not contain the same Siebel runtime repository, then transactions can become corrupt. If you modify the schema or Siebel runtime repository, then you must configure Siebel Remote to upgrade each remote client during the next synchronization. This upgrade is necessary even if this modification does not affect the schema. During typical operations there can be a short moment where the Siebel Server and the remote client contain a different Siebel runtime repository.

For more information, see Overview of the Siebel Remote Architecture.

To upgrade a regional node

  1. Thoroughly test the repository modifications and upgrade steps.

    It is strongly recommended that you thoroughly test the repository modifications and upgrade steps in a separate test environment before you migrate them to a production environment.

  2. Update and distribute the upgraded Siebel runtime repository.

  3. Make sure each user synchronizes with the regional database.

    After synchronizing, each user must not modify the local database until after you finish the upgrade. If you apply these modifications to the Siebel Server on the regional node, then problems might occur.

  4. Wait for Replication Manager to finish applying every transaction to the regional node.

  5. To synchronize the regional node with the parent node, run Replication Agent.

    The parent node is typically the headquarters node. Do not modify the regional node until after you finish the upgrade. If you apply these to the parent node, then problems might occur.

  6. Wait for Replication Manager to finish applying the transactions to the Siebel database on the parent node.

  7. If necessary, disconnect all users, and then stop the server components.

    All upgrades do not require this step.

  8. Apply the upgraded Siebel runtime repository to the headquarters node.

    You can distribute the Siebel runtime repository using Siebel Anywhere. For more information, see Siebel Anywhere Administration Guide.

  9. Finish the upgrade: