Siebel Remote and Replication Manager Administration Guide > Administering Siebel Replication Manager > Process of Administering Siebel Replication Manager >

Upgrading a Regional Node

A change that is made to an object definition must be distributed to the headquarters, regional and local databases. This is known as a minor upgrade. Some examples of changes to object definitions include changes to the behavior of an application or adding extension columns to a table. You can use Siebel Tools to compile the definition of the Siebel application in an SRF (Siebel Repository File). A set of DDL (Data Definition Language) operations represent schema object changes.

In any one schema hierarchy, each Replication Manager instance and each remote client must contain the same database schema and SRF file. If the Siebel Server and the remote client do not contain the same SRF file, then transactions can become corrupt. Any change to the schema or SRF file requires a mandatory upgrade for each remote client during the next synchronization session. This upgrade is necessary even if a change to the SRF file does not affect the schema. During normal operations there can be a short moment where the Siebel Server and the remote client contain a different SRF. The recommendation that this topic describes applies to a long-term configuration change.

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

To upgrade a regional node

1. Thoroughly test the repository changes and upgrade steps.
2. It is strongly recommended that you thoroughly test the repository changes and upgrade steps in a separate test environment before you migrate them to a production environment.Compile and distribute the upgraded SRF file.
3. Make sure each user synchronizes with the regional database.

   After synchronizing, each user must not make any changes to the local database until after you finish the upgrade. Replication Manager stores any changes that users make after this point in the old SRF file and schema. If you apply these changes 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 usually the headquarters node. Do not make any more changes to the regional node until after you finish the upgrade. Replication Manager stores any changes that you make after this point in the old SRF file and schema. If you apply these to the parent node, then problems might occur.

6. Wait for Replication Manager to finish applying the transactions to the server 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 SRF file to the headquarters node.

   For more information on installing a new repository, see Siebel Installation Guide for the operating system you are using.

9. Finish the upgrade:
   • If you use Siebel Anywhere, then see Finishing the Upgrade with Siebel Anywhere.
   • If you do not use Siebel Anywhere, then see Finishing the Upgrade without Siebel Anywhere.

Finishing the Upgrade with Siebel Anywhere

If you use Siebel Anywhere, then you can use it to apply schema changes.

To finish the upgrade with Siebel Anywhere

1. Restart server components, and then make the Siebel application is available to users.
2. Build the upgrade kit for the server database schema.

   For more information, see Siebel Anywhere Administration Guide.

3. Distribute the upgrade kits, and then finish the upgrade.

   For more information, see Siebel Anywhere Administration Guide.

Finishing the Upgrade without Siebel Anywhere

If you do not use Siebel Anywhere, then you must reextract and reinitialize the regional and Remote nodes after you apply the repository changes and synchronize the physical schema.

To finish the upgrade without Siebel Anywhere

1. Synchronize the repository with the physical schema.
2. Allow connected users at the headquarters node to reconnect and continue working using the new SRF file.
3. To create a new database template on the parent node, use Generate New Database.
4. On the parent node, do a database extract of the regional node.
5. Initialize the regional node.
6. Allow connected users on the regional node to reconnect and to resume work using the new SRF file.
7. Generate a new database template on the regional node.
8. Extract each remote client on the regional node.
9. Allow users to reinitialize their local databases and to resume work using the new SRF file.

Language Requirements

Although the language can vary for each instance in any one hierarchy, you must compile the SRF file from the same repository. For example, the SRF file in a replication environment can be in a language that is different from the SRF file in the headquarters environment even if you compile these SRF files from the same SRF file. The language that a remote client uses can be different from the language that another remote client in the same hierarchy uses even if you compile each client from the same SRF file.

Generating Reporting Relationships

If you upgrade to a new version of the Siebel CRM software, or if the denormalized hierarchy structure becomes out of synchronization with the data in the normalized tables, then it might be necessary for you to perform the Generate Reporting Relationships process. This process creates a large number of transactions for Siebel users and regional nodes. It requires significant resources of time, CPU, and memory. For more information, see Siebel Database Upgrade Guide.