Re: Unexpected conversion from AL32UTF8 to WE8ISO8859P1

From: Jonathan Lewis <>
Date: Thu, 8 Jan 2009 12:06:13 -0000
Message-ID: <>

"Jaap W. van Dijk" <> wrote in message
> Hi,
> I have two databases:
> the source, version with AL32UTF8, and
> the target, version, 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.

Just guessing, but possibly the simplest coding option was to convert every two-byte code point that didn't start with a zero into '0xBF'.


Jonathan Lewis

Author: Cost Based Oracle: Fundamentals

The Co-operative Oracle Users' FAQ
Received on Thu Jan 08 2009 - 06:06:13 CST

Original text of this message