Re: Characters beyond ASCII in database ( US7ASCII and UTF8 character set )

On Wed, 05 Dec 2001 05:33:55 GMT, Jesus \(John\) Salvo Jr. <john_at_softgame.com.au> a écrit:
>I just tried exporting that table from the US7ASCII again, but having my
>NLS_LANG=English_Australia.UTF8 and NLS_CHAR=UTF8 ... and then import that
>data into the UTF8 database, also having NLS_LANG=English_Australia.UTF8 and
>NLS_CHAR=UTF8 during the import.
>
>That non-ASCII character, the e with an acute, became the letter I.
>
>So my alternative of exporting the US7ASCII data as UTF8 will not work. I
>tried exporting the US7ASCII data as US7ASCII and then importing it as UTF8
>but it does not allow me to ( I got some IMP error ).

We had a similar problem. Our first database was set (badly) tu US7ASCII, but accepted insert of accentuated text ... A second database was set to ISO-latin-1. and, all 'é'(&eacute;) became 'i'

A workaround was given by oracle support : we had to modify the third byte in our dmp file to set the binary value to the correct charset (seems the character were set on 8bits and following the client-side encoding without conversion in the database)

-- 
Damien