Siebel Database Upgrade Guide > Preparing for Siebel Database Upgrade >

Preparing for a Multilingual Upgrade

Environments: Development, production test, production.

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.

The Database Configuration Utilities validate deployed languages by comparing the status of the language packs installed on the Siebel File System 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 File System, then the validation fails and you cannot continue the upgrade.

Before doing an upgrep, use Siebel Tools to remove or deactivate any records in S_LST_OF_VAL for undeployed languages.

To prepare for a multilingual upgrade

1. Make a list of your deployed languages.

   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.

2. In Siebel Tools, navigate to Screens, System Administration, and then List of Values.
3. Locate the Language Name field, and verify that no languages appear that are not currently deployed.

   Even if you do not have English installed, then some records will have the Language Name value equal English-American. You can ignore these system records.

4. For records where you do not have the corresponding language pack deployed, investigate why these records are present and take one of the following actions:
   • If the record is not needed, delete it.
   • If you are not sure whether the record is needed, remove the check-mark from the Active field. This deactivates the record and prevents it from being included in the validation check performed by the Database Configuration Utilities.

     CAUTION:  Do not deactivate or delete records where the Language Name equals English-American, even if you do not have English-American deployed. These records are needed by the system. The validation process ignores these records.