Space Manager with LiveReorg 9.2 - User Guide

LiveReorg Commands

QUEST_EXEC.LW_START_REORG

Global Operations for Space Manager

How Space Manager Supports Global Operation

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:

• Oracle names—All modules display Oracle names in the characters for your client computer character set. For example, if your computer operating system uses a Japanese character set, names for databases, datafiles, tablespaces, objects, and owners are displayed in Japanese characters. The QSA Installer displays database names in the characters for your database character set. It allows you to specify path names in the characters for your database server character set.
• Datafile and tablespace names—Tablespace Properties allows you to enter datafile and tablespace names in the characters for your client computer character set.
• Script and folder names—All windows for storing and scheduling scripts allow you to enter folder, script, and script owner names in the characters for your client computer character set.
• Script execution—All scripts can be generated and run for data encoded in your database character set. The scripts in question include reorganization scripts. QSA preserves data as it is encoded prior to script execution.
• SQL Editor—The editor displays query results in the characters for your client computer character set. It also allows you to enter Oracle names in these characters. See Use the SQL Editor for a Certain Locale for more information.
• Scripts/Job Monitor—The monitor displays folder, script, and script owner names in the characters for your client computer character set. Status messages and script statements are displayed in U.S. English (US7ASCII) characters. Within script statements, object names, object owner names, and tablespace names are displayed in the characters for your client computer character set.
• Date and time display—All modules display dates and times in the formats for the connecting user’s locale. User locale settings are specified with Windows regional settings on the client computer.

• 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.

How Space Manager Uses Locale Settings

Space Manager and QSA automatically use locale settings for:

• Your database
• The Oracle client being used by Space Manager
• The operating system on your Space Manager client computer

The sections that follow describe how these settings are used.

How Server-side Locales 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.

Multibyte Character Sets and QUEST_EXEC Commands

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.

How Client-side Locales Are Used

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—

• Oracle client—Space Manager uses the character set for your Oracle client to transfer data between the client and your database. All data sent to or received from the client are encoded in this character set.
• Client operating system—Space Manager uses the character set for your client computer operating system to display names and data.
• Connecting user—Space Manager uses the locale for the connecting user to display numbers, currencies, times, and dates.