Kbase P137950: Data gets corrupted when using UTF-8 client with ODBC DataServer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/26/2009 |
|
Status: Unverified
SYMPTOM(s):
Data gets corrupted when using UTF-8 client with ODBC DataServer
When inserting extended characters from a client session started with -cpstream utf-8 -cpinternal utf-8 the string is appended with additional trailing, random characters.
When inserting a string with the length close to a maximum field size limit (on AS/400 character fields are fixed) the query will fail with errors 6182, 2651, and 142
You tried to compare or to update a character field with a value longer than the maximum length. (6182)
Field num: <field-num>, value: <value>. (2651)
** Unable to update <filename> Field. (142)
FACT(s) (Environment):
IBM AS/400 (RISC)
ODBC DataServer
OpenEdge 10.x
CAUSE:
Bug# OE00176055
FIX:
The only workaround is to use single byte code page settings for client sessions (iso8859-1, 1252, etc).
FIX:
Upgrade to 10.1C03 or later