Re: Unexpected conversion from AL32UTF8 to WE8ISO8859P1

From: Jaap W. van Dijk <j.w.vandijk_at_hetnet.nl>
Date: Tue, 13 Jan 2009 01:11:46 -0800 (PST)
Message-ID: <70e50956-7112-41a5-a5e2-d27872718686_at_i24g2000prf.googlegroups.com>

On Jan 8, 11:16 am, "Jaap W. van Dijk" <j.w.vand..._at_hetnet.nl> wrote:
> Hi,
>
> I have two databases:
>
> the source, version 10.2.0.3.0 with AL32UTF8, and
> the target, version 9.2.0.5.0, with WE8ISO8859P1.
>
> I copy a table, containing single and double byte characters, from the
> source database to the target database with "insert into ... select
> from ..." over a database link. The copy is done in a database
> procedure in the target database that is started in a Windows sqlplus
> session.
>
> What happens is that in the target database all the originally double
> byte characters are converted to an inverted question mark, including
> characters that are defined within WE8ISO8859P1.
>
> For instance: a SMALL E ACUTE (code point C265) in the source database
> is converted to an INVERTED QUESTION MARK (code point BF) in the
> target database.
>
> Why is code point C265 not converted to code point E9, which is SMALL
> E ACUTE in WE8ISO8859P1?
>
> Regards,Jaap.

I want to thank all who have contributed to this thread, but I found the cause: I was handed a list of characters with their hexadecimal codes, but now it appears that those were not the UTF-8 codes. For instance SMALL E ACUTE is not C265 but it is C3A9. I managed to find the correct codes and now all is working properly.

Thanks again for your input,
Jaap. Received on Tue Jan 13 2009 - 03:11:46 CST