Re: One char in - different one out

run
select * from nls_session_parameters on both databases and look for 'NLS_LANGUAGE' (if it is not in session_parameters it is either in database or instance parameters)

Chances are your client has been set to US7ASCII. In your 7 bit database no conversion will take place (Oracle just 'accepts' any inserted character) upon retrieval, and your PC has been set to 8-bit character. In your 8-bit database conversion upon retrieval WILL occur, hence you loose the 8th bit.
Resolution: change your NLS_LANGUAGE registry key or environment variable to 8-bit.

Hth,

Sybrand Bakker, Oracle DBA
Tim Tracy <tim.tracy_at_westgroup.com> wrote in message news:38b6d5db_at_wwwproxy3.westgroup.com...
> I am running the same application against two different Oracle databases
> with the same schema. One database is set up with a 7 bit character set,
> the other an 8 bit. When I store a character string with a special
> character in it ( ASCII 133 ), and then retrieve that string, I get
strange
> results.
>
> With the database set up as a 7 bit character set, I get the character I
> stored (ASCII 133). With the database set up as an 8 bit character set, I
> get an ASCII 5. It seems as though I have lost the highest bit on the
> database set up as an 8 bit character set. Can anyone shed some light on
> this and provide a possible resolution?
>
> Thanks.
>
>
Received on Fri Feb 25 2000 - 13:43:01 CST