Korean language issues

This section describes problems with the Korean language.

Server names cannot contain Korean characters

[CR #291309] If you create a server name that includes Korean characters, the server does not start because the <servername>.props file is created incorrectly. You may see errors similar to these in the server’s log file:

Aug 5 15:10:31 2002: Repository::local: failed to open /testarea/jaguar.412.d10/Repository/Server/??1.props
Aug 5 15:10:31 2002: Server is running in 1PC Transaction mode.
Aug 5 15:10:31 2002: Starting Jaguar CTS 
Aug 5 15:10:31 2002: Server's native codeset is iso_1
Aug 5 15:10:31 2002: Library: 'libjjdk12.so' for component type 'java'
Aug 5 15:10:31 2002: Repository::local: failed to open /testarea/jaguar.412.d10/Repository/Server/??1.props
Aug 5 15:10:31 2002: Java JIT Compiler enabled
Aug 5 15:10:31 2002: Java component debugging disabled
Aug 5 15:10:32 2002: Java virtual machine initialized: java version 1.3.1_01
Aug 5 15:10:32 2002: Java virtual machine initialized: Java HotSpot(TM) Client VM (version 1.3.1_01, mixed mode)
Aug 5 15:10:32 2002: Bad Repository: /testarea/jaguar.412.d10/Repository
Aug 5 15:10:32 2002: java.io.FileNotFoundException: /testarea/jaguar.412.d10/Repository/Server/???1.props

Oracle databases and Korean language data

[CR #289080] Some Oracle databases support iso_* character sets but not the UTF-8 character set. If you set the server’s Codeset property to UTF-8, Korean language data is inserted into an Oracle database incorrectly. When the codeset is set to iso_1, Korean language data is inserted correctly.

Copyright © 2005. Sybase Inc. All rights reserved.

View this release bulletin as PDF