Re: Special Characters Created on a UNIX system with HP Terminal on US7ASCII

On Jul 17, 3:46 pm, gk24 <g..._at_nurfuerspam.de> wrote:
> Hi all,
>
> I have a customer who uses an application on a UNIX server. The
> database (US7ASCII, 9i) is on a Windows server. The system was
> migrated from a 2-tier solution before meaning the application and the
> database were on UNIX before.
>
> The problem is that clients and SQLPlus on Windows computers get wrong
> special character like German Umlaute or °-sign.
>
> (...)
>
> The nls_lang settings are US7ASCII on all three tiers. The dump
> function shows the e.g. the German "ü" is stored as &CF in the
> database.
>
> Any help appreciated.
>

>From the "Globalization Support Guide":
US7ASCII / U.S. 7-bit ASCII / US / Bits: 7 / ASCII

So you are telling us that you used US7ASCII to store German umlauts? This is just wrong. US7ASCII is just 0x00 -> 0x7F but the characters you are talking about are 0x80 -> 0xFF and so cannot be correctly stored in an US7ASCII character set column.

Anyway, if your client NLS_LANG setting has the same setting as the database then this means that _no_ character set conversion will take place btw. the bytes(characters) your client wants to insert and the data that actually gets inserted.

> The nls_lang settings are US7ASCII on all three tiers. The dump
> function shows the e.g. the German "ü" is stored as &CF in the
> database.
>

"ü" (ue) should be 0xFC (Typo?)

All in all I would classify a US7ASCII DB used to storing ISO-8859-1 Data (The standard encoding with german) as an "undefined state" and you may be out of luck here.

br,
Martin Received on Wed Jul 18 2007 - 10:28:09 CDT