Re: replication: problem with character "degree" celcius

From: Frank van Bortel <frank.van.bortel_at_gmail.com>
Date: Tue, 12 Jun 2007 22:06:40 +0200
Message-ID: <f4mucf$8b6$1@news1.zwoll1.ov.home.nl>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Charles Hooper wrote:
> On Jun 12, 7:46 am, sybrandb <sybra..._at_gmail.com> wrote:

>> On Jun 12, 1:39 pm, Charles Hooper <hooperc2..._at_yahoo.com> wrote:
>>> The problem appears to be that Oracle permitted your application to
>>> store an 8 bit ASCII value in a 7 bit ASCII database: 176 > 127.
>>> Charles Hooper
>>> IT Manager/Oracle DBA
>>> K&M Machine-Fabricating, Inc.
>> This will happen if client is 7-bit ASCII AND server is 7-bit ASCII.
>> In that case there will be no conversion and everything even > 128
>> will pass.
>>
>> --
>> Sybrand Bakker
>> Senior Oracle DBA

>
> Thanks for the explanation.
>
> If the OP were to convert the source database from 7 bit ASCII to 8
> bit ASCII (WE8ISO8859P1), would that resolve the problem without
> losing the existing high bit of the ASCII characters for ASCII
> characters >= 128, so that ASCII 176 does not become ASCII (176 -
> 128)?
>
> Charles Hooper
> IT Manager/Oracle DBA
> K&M Machine-Fabricating, Inc.
>

As I understand replication, the client to the source, is the target database. So there's a WE8ISO8859 "client" to a US7ASCII source (who uses US7ASCII nowadays?!?). Changing the client character set to US7ASCII would resolve this. E.g. setting the environment variable (not the db character set!) to US7ASCII.
A simple test with the SQL*Plus from the WE8 target environment would prove it, after setting the character set to US7ASCII. - --
Regards,
Frank van Bortel

Top-posting is one way to shut me up...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFGbvzQLw8L4IAs830RAkrbAJ44pYnFPDd7G8Ef1PqugcApLlTMZACgkeWX oopLiv4C8kJoVejn11EHO40=
=WlsB
-----END PGP SIGNATURE----- Received on Tue Jun 12 2007 - 15:06:40 CDT