Upgrade Planning for Multilingual Siebel Deployments

Environments: Development, Test and Production.

Platforms: Windows, UNIX, IBM z/OS.

The upgrade process upgrades both the primary (base) language and all deployed languages.

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 might have ENU as the primary language and FRA, and JPN as its non-primary languages. Replacing the primary language, ENU 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 user interface 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.

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