This documentation applies to the 8.1 version of Remedy IT Service Management Suite, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Preparing to upgrade on a Unicode database

This topic contains the following material:

Before you begin

If you are installing BMC Remedy AR System for the first time and you want to use Unicode, make sure your database is configured to use Unicode.

Warning

Each database client library has special mechanisms for specifying the codeset in which database clients attempt to communicate with the AR System server. If these mechanisms specify a codeset that is not consistent with the codeset that the AR System server and upgrade programs expect, errors and data corruption can occur. The following procedure can help you avoid this problem.

Note

If you are installing the Russian version of the BMC Remedy ITSM applications, ensure that you are using a non-unicode database. The Russian version does not support unicode. The installed Russian version cannot coexist with other installed language versions with the exception of the English version.

To prepare your host computer for a Unicode BMC Remedy AR System installation or upgrade

  1. (UNIX only) Set the LANG environment variable for the locale you will be using.
    • Make sure you have installed UTF-8 locales in which you plan to run BMC Remedy AR System programs.
    • Make sure you use the correct spelling and capitalization for your particular system (for example, on Solaris, you might enter en_US.UTF-8 ). To find the locales that correspond to the language you want to use, use the locale -a command. See your UNIX system documentation for information about locale settings.
    • To set the locale of the installation, the server installation script uses the locale of the shell it is run from. For example, to install a server on Solaris that runs in the en_US.UTF-8 (U.S. English, Unicode/UTF-8 character encoding) locale, set your shell's locale by setting the environment variables LANG and LC_ALL to en_US.UTF-8 before installing BMC Remedy AR System. 
    • During installation, the BMC Remedy AR System installer sets up the arsystem script with the correct values for LANG variable. The arsystem script launches armonitor, which launches the programs mentioned in the armonitor.conf file; each of these programs inherits the environment variables established in the arsystem script.
  2. (Oracle only) If you are installing an Oracle Unicode BMC Remedy AR System on a Microsoft Windows operating system, set the value of the NLS_LANG registry setting.
    Depending on your system's configuration, the setting's key looks similar to the following:
    HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_oracle_home_name\NLS_LANG
    Oracle defines the NLS_LANG value as LANGUAGE_TERRITORY.CHARACTERSET, for example, AMERICAN_AMERICA.AL32UTF8.
    The CHARACTERSET value AL32UTF8 tells the Oracle client library to send and receive character data as UTF-8. (Do not use the CHARACTERSET value UTF8, which is obsolete.)
    This setting affects all Oracle database clients that use the Oracle installation named by oracle_home_name.
    1. Verify that the NLS_LANG environment variable is set correctly.
    2. Set the NLS_LENGTH_SEMANTICS=BYTE initialization parameter on the Oracle database instance.
      Although the BMC Remedy AR System server enables you to request that character fields be measured in characters, the server still communicates with the database in bytes.
      For more information, see Oracle Metalink Note 144808.1, "Examples and limits of BYTE and CHAR semantics usage."

      Warning

      BMC Remedy AR System does not support the CHAR setting. If your database administrator (DBA) changes NLS_LENGTH_SEMANTICS value  from BYTE to CHAR when reconfiguring NLS_INSTANCE_PARAMETERS, the data in the AR System server will be corrupted. The NLS_LENGTH_SEMANTICS parameter must be set to BYTE in NLS_INSTANCE_PARAMETERS when the Oracle database server is started.

  3. (IBM DB2 only) Set the DB2CODEPAGE setting.
    The DB2CODEPAGE environment variable setting determines the client codeset. If the environment variable is not set, the DB2 client library derives a DB2CODEPAGE value from the current locale. On UNIX systems, this value is valid if the server or upgrade program has been started in a UTF-8 locale. On Windows systems, you must explicitly set the environment variable to start the server correctly.
    Use the following syntax to set the DB2CODEPAGE environment variable.
    • UNIX /bin/sh file: DB2CODEPAGE=1208; export DB2CODEPAGE
    • UNIX /bin/csh file: setenv DB2CODEPAGE 1208
    • Windows batch file (if starting the server manually): set DB2CODEPAGE=1208
      You can use the Windows Control Panel to set the environment variable globally or set it for a specific user.

Note

Sybase determines its client character set from the locale set by the LANG environment variable. Microsoft SQL Server is a Unicode database, so you do not need to perform any steps to set it up.

To upgrade BMC Remedy AR System 6.3 and later servers with a Unicode database to BMC Remedy AR System 7.0.01 and later

  1. Back up the database components, objects, forms, and data.
  2. On Windows systems, run the installer in the same locale that you ran the original BMC Remedy AR System server.
    For example, if the original server ran in a Japanese locale, run the upgrade installer in the same Japanese locale.
  3. On UNIX systems, run the installer in the Unicode version of the locale in which you ran the original AR System server.
    For example, if the server ran in the ja_JP.eucJP locale, run the installer in the ja_JP.UTF-8 locale. Locale names vary across UNIX variants and versions.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments