This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

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

Unicode support

A product that provides Unicode compliance is written using the Unicode character coding system, which means Unicode data can flow from database to client without any conversion occurring. A product that provides Unicode database support enables the database to contain Unicode characters but converts them between the database and the product. Any product that accesses the database, however, still uses a native character set.

The Unicode database option enables you to have multi- and single-byte forms, data, and workflow stored in the same database or database instance. Unicode database support in AR System enables you to use multiple languages on one AR System server. You are no longer restricted by the operating system's locale.

The following section explains the Unicode support for BMC Remedy AR System.

Unicode database support for forms

The Unicode database option enables you to have multi- and single-byte forms, data, and workflow stored in the same database or database instance.

Note

To use BMC Remedy AR System with the Unicode database option to support multiple languages using a shared database, you must install an English version of BMC Remedy AR System server before you install multi-language AR System servers.

Unicode database support in BMC Remedy AR System 7.0.00 and later enables you to use multiple languages on one AR System server. You are no longer restricted by the operating system's locale.

Unicode support for AR System database types

Each database type supported by BMC Remedy AR System supports Unicode at one of the levels listed in the following table.


Unicode support for AR System database types

Unicode support level

Database type

Comments

Database instance

Sybase, Oracle

For these database types, you must configure the database instance before you install the new AR System database.

Note

(Oracle only) If you use an Oracle AR System database with the Unicode database option, problems might occur if the NLS_LENGTH_SEMANTICS parameter is not set to BYTE in the AR System database and in the database server instance. See Preparing to install on a Unicode database and Preparing to upgrade on a Unicode database.


Specific column type

Microsoft SQL Server

Uses Unicode data types nchar, nvarchar, and ntext.

Database

DB2

No database configuration required.

During installation, the BMC Remedy AR System installer gives you the option of creating a Unicode database. You can safely do this if you meet the following requirements:

  • You are not installing on an existing AR System database.
  • Your database supports Unicode at the column or tablespace level, or you configured your database instance for databases that support Unicode at the database-instance level.

Warning

If you have an AR System database, you must first migrate it to Unicode before upgrading your AR System server. If you choose the Unicode database option during an upgrade install against a non-Unicode AR System database, you will corrupt your database. See the next section, Database migration to Unicode.

Database migration to Unicode

If you are upgrading an BMC Remedy AR System that already has a database, you must migrate the database to Unicode before proceeding with the BMC Remedy AR System upgrade installation. This ensures your data integrity.

The following procedures describe how to migrate your database to Unicode database. For more details, see your database documentation.

Migrating an Oracle database to Unicode

To migrate an Oracle database, follow these general steps. For detailed information, see your Oracle documentation.

  1. Confirm your Unicode Oracle database is using AL32UTF8 character set.
    The character set is defined during the creation of the Unicode database. There is no change on a character set for an existing database. During the creation of the database, the response to the prompt for character set is AL32UTF8. The Oracle database engine performs any conversion required during import of the original (non-Unicode) into the new database.
  2. Perform a full export and import on the whole database.

    Note

    UTF-8 columns usually store fewer characters compared to non-Unicode columns. In these cases, you might be introducing data truncation. For more information, see your Oracle documentation.

Migrating a Microsoft SQL Server database to Unicode

To migrate a Microsoft SQL Server database, follow these general steps. For detailed information, see your Microsoft SQL Server documentation.

  1. Create columns in the target database that correspond to the source database as shown in the following table.

    Source and target column database types

    Source column type

    Target column type

    char

    nchar

    varchar

    nvarchar

    text

    ntext

  2. Migrate your data on a column-by-column basis.

    Warning

    If the database has Unicode and non-Unicode columns, BMC Remedy AR System will not work.

Migrating a DB2 database to Unicode

For DB2 databases, the database character set is a configuration parameter that you cannot update. Therefore, existing non-Unicode DB2 AR System databases cannot be migrated to Unicode.

Migrating a Sybase database to Unicode

To migrate a Sybase database, follow these general steps. For detailed information, see your Sybase documentation.

  1. Export the database.
  2. Change the Sybase default character set to UTF8.
  3. Import the data back into the Sybase database.
  4. Update the tables containing text columns.

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