The server code set

When the database server creates a file whose file name contains non-ASCII characters, the server locale must support these characters.

Before you start a database server, you must set the SERVER_LOCALE environment variable to the name of a locale whose code set contains these non-ASCII characters.

For example, suppose you want a message log with the UNIX™ path /A1A2B1B2/C1C2D1D2, where A1A2, B1B2, C1C2, and D1D2 are multibyte characters in the Japanese SJIS code set. For example, suppose you want a message log with a UNIX path /A1A2B1B2/C1C2D1D2, where A1A2, B1B2, C1C2, and D1D2 are multibyte characters. To enable the database server to create this message-log file on its computer:
  1. Modify the MSGPATH parameter in the ONCONFIG file.
    For UNIX:
    MSGPATH /A1A2B1B2/C1C2D1D2   
# multibyte message-log filename
    For Windows™:
    MSGPATH \A1A2B1B2\C1C2D1D2   
# multibyte message-log filename
  2. Set the SERVER_LOCALE environment variable on the server computer to the Japanese SJIS locale, ja_jp.sjis.Set the SERVER_LOCALE environment variable on the server computer to the appropriate multi-byte locale.
  3. Start the database server with the oninit utility.

When the database server initializes, it assumes that the operating system is 8-bit clean and creates the /A1A2B1B2/C1C2D1D2 message log on UNIX, or the \A1A2B1B2\C1C2D1D2 file on Windows.