Re: Problems with NLS_LANG settings

From: I hate Spam <tbf_at_cn.stam.dk>
Date: Thu, 01 Nov 2001 00:27:34 +0100
Message-ID: <cu11utcpde3qa9hgd6kgqtq725iupqd4f3_at_4ax.com>


On Wed, 31 Oct 2001 15:53:28 +0100, "Ralf Pickart" <ralf.pickart.NOSPAM_at_gmx.net> wrote:

>Hi,
>
>until now we used the WE8ISO8859P1 characterset for our databases. To
>support other languages/charsets I have to set up a database with multibyte
>unicode characterset. Ok, so far so good... I choose UTF8 as database
>characterset and set NLS_LANG on client side to this value too (environment
>variable and windows registry).

I am not sure if this relates to your problem, but if you have the same NLS_LANG on your client as defined in your database the SQLNET does not make any attempt to check or convert the data. I know this can make problems in some applications.

Yours Hans Erik Busk
tbf_at_cn.stam.dk Received on Thu Nov 01 2001 - 00:27:34 CET

Original text of this message