Table of Contents

  1. Preface
  2. Upgrade Overview
  3. Before You Upgrade the Domain on Windows
  4. Before You Upgrade the Domain on UNIX
  5. Prepare for the Upgrade
  6. Upgrade the Domain
  7. Upgrade the Domain with Changes to Node Configuration
  8. Before You Upgrade the Application Services
  9. Application Service Upgrade
  10. Informatica Client Upgrade
  11. After You Upgrade
  12. Updating the DynamicSections Parameter of a DB2 Database
  13. Upgrade Checklist

Upgrading from Version 10.0

Upgrading from Version 10.0

Configure Locale Environment Variables

Configure Locale Environment Variables

Use LANG, LC_CTYPE, or LC_ALL to set the UNIX code page.
Different UNIX operating systems require different values for the same locale. The value for the locale variable is case sensitive.
Use the following command to verify that the value for the locale environment variable is compatible with the language settings for the machine and the type of code page you want to use for the repository:
locale -a
The command returns the languages installed on the UNIX operating system and the existing locale settings.
Locale on Linux
All UNIX operating systems except Linux have a unique value for each locale. Linux allows different values to represent the same locale. For example, “utf8,” “UTF-8,” “UTF8,” and “utf-8” represent the same locale on a Linux machine. Informatica requires that you use a specific value for each locale on a Linux machine. Make sure that you set the LANG environment variable appropriately for all Linux machines.
Locale for Oracle database clients
For Oracle database clients, set NLS_LANG to the locale that you want the database client and server to use with the login. A locale setting consists of the language, territory, and character set. The value of NLS_LANG depends on the configuration.
For example, if the value is american_america.UTF8, set the variable in a C shell with the following command:
setenv NLS_LANG american_america.UTF8
To read multibyte characters from the database, set the variable with the following command:
setenv NLS_LANG=american_america.AL32UTF8
You must set the correct variable on the Data Integration Service machine so that the Data Integration Service can read the Oracle data correctly.

Updated May 14, 2019


Explore Informatica Network