Re: char set still issues

From: Sybrand Bakker <postbus_at_sybrandb.demon.nl>
Date: Thu, 19 Apr 2001 20:54:56 +0200
Message-ID: <tdud027778ird8_at_beta-news.demon.nl>


"cathy gao" <cgao_at_sprint.ca> wrote in message news:xFDD6.3382$Ar3.75239_at_newscontent-01.sprint.ca...
> hi sybrand,
> i have a problem which looks similar or related to this one.
> pls advise.
>
> here's my situation, we have a production database oracle 8.1.5.1 which
 runs
> a WE8ISO8859P1 nls_character_set -built database.
>
> we have a development database which was built with a US7ASCII charset.
>
> it seems to work okay from the apps, but lately exports and imports are
> internmittently
> getting stuck, and apps seems to hang when ask to display 'imported' data.
> when new data
> are created within the apps, it seems ok.
>
> is there a genuine issue exporting and importing between databases of
> different
> character set although the oracle dbms version and os are identical?
>
> your help will be greatly appreciated.
>
>
> any solutions.
>
> tnx.
>
> cathy gao
> ----- Original Message -----
> From: "Sybrand Bakker" <postbus_at_sybrandb.demon.nl>
> Newsgroups: comp.databases.oracle.tools
> Sent: Thursday, April 19, 2001 10:48 AM
> Subject: Re: NLS_CHARACTERSET ?
>
>
> > On Thu, 19 Apr 2001 15:41:42 +0400, "Andrei V. Kirilenkov"
> > <kirilenkov_at_sovintel.net> wrote:
> >
> > >I have created my DB with
> > >NLS_CHARACTERSET = CL8ISO8859P5
> > >NLS_NCHAR_CHARACTERSET = CL8ISO8859P5
> > >which is ISO 8859-5 Latin/Cyrillic acoording to the documentation.
> > >But after trying to insert the Russian string into a table I get only
> > >'???????????????'
> > >
> > >Does anybody know what is wrong here?
> > >
> > >client nls_lang is AMERICAN_AMERICA.WE8ISO8859P1 (if matters at all)
> > >
> > Yes that matters at all. It is the very reason for your problem.
> > Change the last bit after the . to CL8ISO8859P5
> > and retry.
> >
> > Hth,
> >
> > Sybrand Bakker, Oracle DBA
>
>
>

Well of course any export from server1 into server2 would create havoc. Either you set NLS_LANG to American_America.US7ASCII and you will loose bit 7 on export, with no problems on import (provided you don't change NLS_LANG in between)
or you set it to American_America.WE8ISO8859P1 and (again provided you don't change NLS_LANG) it will be chopped off during import, because the target characterset is not identical or a superset. The only other 'solution' I have is start out with WE8ISO8859P1 on export and change it to US7ASCII on import. As import thinks the data doesn't need to be converted , the data should end up with bit 7 set appriopately. This is however a bad trick.

The other way around however would work without problems.

Morale: No other choice than to change the characterset of server2.

Hth,

Sybrand Bakker, Oracle DBA Received on Thu Apr 19 2001 - 20:54:56 CEST

Original text of this message