Database server code-set conversion

These topics summarize the code-set conversion that the database server performs.

For more general information about code-set conversion, see Perform code-set conversion.

The HCL OneDB™ database server automatically performs code-set conversion between the code sets of the server-processing locale and the server locale when the following conditions are true:
  • The CLIENT_LOCALE, DB_LOCALE, and SERVER_LOCALE environment variables are set such that the code sets of the server-processing locale and the server locale are different.
  • A valid code-set conversion exists between the code sets of the server-processing locale and server locale.

For a list of files for which HCL OneDB database servers perform code-set conversion, see GLS support by HCL OneDB database servers. For information about GLS code-set conversion files, see Code-set-conversion files.

Enterprise Replication supports replication between database servers that use different code sets. See Enabling code set conversion between replicates for more information.

After the database server creates the operating-system file, it has generated a file name and written file contents in the code set of the server locale (the server code set). Any HCL OneDB product or client application that needs to access this file must have a server-processing locale that supports this same server code set. You must ensure that the appropriate CLIENT_LOCALE, DB_LOCALE, and SERVER_LOCALE environment variables are set so that the server-processing locale supports a code set with these non-ASCII characters. For more information about the server-processing locale, see Determine the server-processing locale.

The database server checks the validity of a file name with respect to the server-processing locale before it references the file name.