Bookshelf Home | Contents | Index | PDF |
Siebel Remote and Replication Manager Administration Guide > Administering Siebel Replication Manager > Process of Administering Siebel Replication Manager > Upgrading a Regional NodeYou 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.
Finishing the Upgrade with Siebel AnywhereIf you use Siebel Anywhere, then you can use it to apply schema modifications. For more information, see Siebel Anywhere Administration Guide. To finish the upgrade with Siebel Anywhere
Finishing the Upgrade without Siebel AnywhereIf you do not use Siebel Anywhere, then you must reextract and reinitialize the regional and Remote nodes after you apply the Siebel repository modifications and synchronize the physical schema. To finish the upgrade without Siebel Anywhere
Language RequirementsAlthough the language can vary for each instance in any one hierarchy, you must create the Siebel runtime repository from the same Siebel development repository. For example, the Siebel runtime repository in a replication environment can be in a language that is different from the Siebel runtime repository in the headquarters environment, even if you generate both of these Siebel runtime repositories from the same Siebel development repository. The language that a remote client uses can be different from the language that another remote client in the same hierarchy uses even if both clients use a Siebel runtime repository created from the same Siebel development repository. Generating Reporting RelationshipsIf 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 do 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. |
Siebel Remote and Replication Manager Administration Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |