Locale-specific support for utilities

This section provides information that is specific to the use of the GLS feature by database server utilities.

For a complete description of utilities, see your HCL OneDB™ Administrator's Reference.

For information about database server utilities for auditing, see the HCL OneDB Security Guide.

Enterprise Replication supports replication between database servers that use different code sets. This functionality is useful for converting servers to the Unicode code set with minimal application downtime, for converting servers from one code set to another, and for replicating data between servers in different locals. You enable replication between code sets by using the UTF8 option when creating the replicate definition. See Enabling code set conversion between replicates for more information.

Database server utilities and SQL utilities are client applications that request information from an instance of the database server. Therefore, these utilities use the CLIENT_LOCALE, DB_LOCALE, and SERVER_LOCALE environment variables to obtain the name of a nondefault locale, as follows:
  • If a database utility is to use a nondefault code set to accept input (including command-line arguments) and to generate output, you must set the CLIENT_LOCALE environment variable.
  • If a database utility accesses a database with a nondefault locale, you must set the DB_LOCALE environment variable.
  • If a database utility causes the database server to write data on the server computer that has a nondefault code set, you must set the SERVER_LOCALE environment variable.

These utilities also perform code-set conversion if the database and the client locales support convertible code sets. For more information about code-set conversion, see Perform code-set conversion.

Changes to locale environment variables should also be reflected in the Windows™ registry database under HKEY_LOCAL_MACHINE.