Siebel Database Upgrade Guide > Siebel Database and UI Upgrade Planning >

Upgrade Planning for Multilingual Siebel Deployments

Upgrades from: All Supported Siebel releases.

Environments: Development, production test, production.

Databases: All databases.

Platforms: Windows, UNIX, IBM z/OS.

As of Siebel CRM 8.0, the upgrade process upgrades both the primary (base) language and all deployed languages. This applies to upgrades from Siebel 7.x on both non-Unicode and Unicode databases.

CAUTION:  Each multilingual deployment must contain a primary language as well as those that are designated as secondary, or non-primary. For instance, a deployment may have ENU as the primary language and FRA, and JPN as its non-primary languages. Replacing ENU, the primary language in this example, with one of the non-primary languages during upgrade is not supported, as it will result in severe data corruption, making recovery extremely difficult.

The development and production upgrep process does the following for the primary language and all deployed languages:

  • (Development upgrep). Imports UI strings into the Prior Standard Repository, New Customer Repository, and New Siebel Repository.
  • Imports seed data into the database.
  • In the S_LST_OF_VAL table, an SQL script activates all newly imported records and configures them to support multilingual lists of values (MLOVs). LOVs remain enabled for the primary language.
  • For upgrades from Siebel 7.0.x, an SQL script makes required changes to the Marketing demand creation program table (S_SRC_DCP) and to the demand creation LOV or MLOV.

No language-related manual tasks are required to upgrade the deployed languages, except where noted.


Prior to starting a development or production upgrep, you must have installed the new release's language packs for all deployed languages.

The Database Server Configuration Utilities validate deployed languages by comparing the status of language packs installed on the Siebel Server with the language IDs of records in the S_LST_OF_VAL table. If there are Language IDs in S_LST_OF_VAL but no corresponding deployed language on the Siebel Server, the validation fails and you cannot continue the upgrade.

Prior to starting a development or production upgrep, you must review the records in S_LST_OF_VAL, using Siebel Tools. Remove or deactivate records for languages that you do not have deployed.

For more information, see Running the Siebel Database Configuration Wizard Under Windows, or Running the Siebel Database Configuration Wizard Under UNIX depending on your operating system.

CAUTION:  Regardless of whether you have American-English deployed, there will be records in S_LST_OF_VAL with Language Name = English-American. Do not deactivate or delete these records. The validation process ignores them.


The following restrictions apply to multilingual upgrades:

  • Installed languages must be deployed. If you have installed a language but not deployed it, the language will not be upgraded.

    A deployed language is one where you have installed the language pack, imported the UI strings into the Siebel Repository, imported the seed data into the database, activated the seed data records added to S_LST_OF_VAL, and configured the records for MLOVs.

  • You cannot select which languages to upgrade. The Upgrade Wizard upgrades all deployed languages.
  • You cannot add or drop a language during an upgrade. If you want to add a language that is not currently deployed, do so after the upgrade. For more information on adding new languages, see Global Deployment Guide and Siebel Installation Guide for the operating system you are using.
Siebel Database Upgrade Guide Copyright © 2008, Oracle. All rights reserved.