Frank van Bortel said the following on 25.04.2005 13:55:
> Ralf Bender wrote:
>
>>Frank van Bortel said the following on 25.04.2005 11:05:
>>
>>
>>>Ralf Bender wrote:
>>>
>>>
>>>>Hello,
>>>>
>>>>import and export are driving me crazy.
>>>>
>>>>I've got a source database ORA 7.3 which I exported first with a
>>>>character set in the enviroment variable US7ASCII. The original database
>>>>was created with AMERICAN_AMERICA.US7ASCII.
>>>>
>>>>I will import this to a target database ORA 8.1 with a character set of
>>>>WE8ISO8859P1.
>>>>
>>>>After importing i loose all german special characters.
>>>>
>>>>I try a second export and set the enviroment at the source database to
>>>>GERMAN_GERMANY.WE8ISO8859P1.
>>>>
>>>>After importing I have also no german special characters.
>>>>
>>>>Can someone tells me what I'm doing worng here or what's the correct
>>>>way.
>>>>
>>>>thx
>>>>ralf
>>>
>>>
>>>
>>>Actually, I can hardly believe you had *any* special character in
>>>that databse, or it was not *created* with US7ASCII.
>>>Special characters are in the extended characterset, which requires
>>>the use of the 8th bit; obviously, something US7ASCII doesn't
>>>allow.
>>>
>>>If the 7.3 databse *did* have special characters, export using
>>>AMERICAN_AMERICA.US7ASCII, and import using that, too.
>>>
>>>You should *not* have warnings about characterset conversions!
>>
>>
>>I don't really understand what happens here.
>>I create a new database with US7ASCII and run the importfile also in
>>US7SCAII.
>>After that, I changed the characterset of the whole database to
>>WE8ISO8859P1 and I see german special characters!
>>
>>But, how can i be sure that only the special characters are changed and
>>not other data....
>>
>>
>>
>>
>>
>
> 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;
ralf
Received on Mon Apr 25 2005 - 10:02:30 CDT
