Ralf Bender wrote:
[snip!]
>>>
>>
>> Are you sure the special characters are stored in varchar2 columns,
>> and not in e.g. long raw or long columns?
>> Long would suffer from characterset conversions; long raw would not.
>
>
> mmmhh, I'm not sure. The old DB got 10.000 tables and don't really know
> all of them and their data.
> So, I think i have to leave it in US7ASCII. Changing the enviroment
> variable of a client to Oracle standard will also bring up my special
> characters... that's nice.
>
> But, if I do so I got a new problem with my clients. All existing
> databases works with client enviroment GERMANY_GERMAN.WE8ISO8859P1. And
> that won't show the correct characters.
>
> Do you think/know it's enough to change the session variable with alter
> session:
> alter session set nls_territory = AMERICA;
> alter session set nls_language= AMERICAN;
>
As you are not sure what is going on, I most
certainly don't know, either.
Based on that, I can only suggest: give it a try,
it may work. And it won't harm, as long as you
only read data, not alter or insert
--
Regards,
Frank van Bortel
Received on Mon Apr 25 2005 - 10:13:45 CDT
