Siebel Database Upgrade Guide > Application Planning for a Siebel Upgrade >

Upgrade Planning for Siebel String Translation

Upgrades from: Siebel 7.0.x and 7.5.x.

Platforms: Windows, UNIX, IBM z/OS.

Siebel 7.7 introduced a new method of generating data-migration SQL. Based on the language for the Siebel upgrade process, the Siebel upgrade scripts are created accordingly.

NOTE:  To avoid unintended results, you must perform your upgrade in the same language as that of the base language in the prior release.

When the Database Configuration Wizard is started, the sqlgen utility generates the Siebel upgrade scripts based on the information located in the upgfile.xml file. When the Database Configuration Wizard completes, SQL scripts are generated, and replace the placeholders in the upgfile.xml with the language-specific values located in the dbsrvr/<LANG>/upglocale.<LANG> file.

In the following example, the locale file is upglocale.fra, for a FRA based installation. The upgfile.xml contains the following statement:

update S_DOC_QUOTE

set QUOTE_SUB_TYPE_CD = &apos;<XTL_STRING>Private</XTL_STRING>&apos;

where QUOTE_TYPE = &apos;<XTL_STRING>Template</XTL_STRING>&apos;

The placeholders <XTL_STRING>Private</XTL_STRING>' and '<XTL_STRING>Template</ XTL_STRING> are values that the sqlgen utility changes during the upgrade. The XTL_STRING values are replaced based on what the sqlgen utility locates as a match for the Private and Template strings in the upglocale.fra file, located under dbsrvr/FRA. For this example, the FRA base language dictates Template = Modèle and Private = Privé.

CAUTION:  If you modified string mappings in your previous Siebel release, you must contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services in order to modify standard upgrade scripts accordingly. If you do not, your Siebel application data from the prior release may not be migrated to the new Siebel release's data model.