Space Manager and the QSA Server Agent are globalized applications that support various locales, languages, and character sets. Supported locales include Japanese and Western European locales. Supported character sets include multibyte character sets and ASCII. (QSA is Space Manager’s script execution engine.)
Space Manager and QSA must be run in an environment where the same or compatible locales are used for your Oracle database, your Oracle client, your database server operating system, and your client computer operating system. All must use the same character set or compatible character sets.
Please note that although Space Manager can be run for various locales, it is not localized for any particular locale. Also note that it supports single-language-at-a-time (SLAAT) operation as opposed to multi-locale operation.
This section identifies the ways in which Space Manager supports locale settings for a database environment:
Messages and field labels—All modules display messages and field labels in U.S. English characters (US7ASCII).
Note Certain languages are not displayed correctly by Space Manager. These include bidirectional languages such as Hebrew and Arabic. They also include complex script languages such as Hindi and Thai.
Space Manager and QSA automatically use locale settings for:
The sections that follow describe how these settings are used.
On your database server, QSA uses locale settings for your database to communicate with the database during script execution. The settings in question are for language, territory, and character set. These are specified with the NLS_LANGUAGE, NLS_TERRITORY, and NLS_CHARACTERSET database parameters when a database is created.
QSA does not use locale settings for the database server operating system. However, it reports these settings in log files. See How Space Manager Reports Locale Settings for more information.
When a database uses a multibyte character set such as JA16SJIS or JA16EUC, QSA converts its QUEST_EXEC commands to UNICODE during script execution. All names in the commands are also converted.
QSA does not convert commands for databases that use a single-byte or UNICODE character set such as AL24UTFFSS, UTF8 or AL32UTF8. QSA reports on UNICODE translation in log files. See How Space Manager Reports Locale Settings for more information.
Note If an object name or username contains a character that cannot be converted to UNICODE, script execution fails with the following error: “QSA-20395—Could not parse script”. For assistance in recovering from the error, contact Quest Software Support.
On your client computer, Space Manager uses the character set for the Oracle client, the character set (ANSI code page) for the operating system, and the locale for the connecting user—