Re: Export/Import and NLS

On Sun, 21 Feb 1999 10:24:00 -0800, "Pei L. Ku" <pku_at_gte.net> wrote:

Hi Pei,

1 - the import utility can perform characterset conversion 2 - the only thing that is important is the value of the environment variable NLS_LANG (unix) or the registry key NLS_LANG on win95/NT. If this variable has not been set US7ASCII will be used, regardless of init.ora parameters
3 From what I gather from your post, you actually need conversion. This means your env var of registry has to end in .WE8ISO8859P1 You have been able to get those characters in in a US7ASCII database, quite likely they don't display properly, what happens during import is bit 7 is stripped of, which is no conversion because by design bit 7 is not used. As you don't want that you have to specify an eight bit character set on import, thus WE8ISO8859P1.

Hth,
Sybrand Bakker, Oracle DBA

>Hello,
>
>I'm exporting data from a Oracle 7.2.3 database. This database was created
>with US7ASCII char set. Some tables in this database, however, contains
>Western European characters (e.g., ascii value 128 to 255). On a different
>machine I've created a 8.0.4 database using WE8ISO5589P1 (or something like
>that). When I import the 7.2.3 export into the 8.0.4 database, I noticed
>that all ascii in the 128 to 255 range got converted to ascii b/w 0 and 127.
>
>I did look up Oracle manuals and in several places it mentioned that if I
>set NLS_LANG to the char set of export file then I'll be ok. So I set
>NLS_LANG to _.US7ASCII before start the import. Didn't work. I then tried
>several other permutations of NLS_LANG values on both the import and export
>side and still I had no luck.
>
>What gives? btw, I've verified that the export does contain ascii 128 to
>255 (by importing the data back into the 7.2.3, US7ASCII database), so the
>unwanted conversion is occurring on the import side.
>
>thanks
>
>Pei
>
>

Sybrand Bakker, Oracle DBA Received on Sun Feb 21 1999 - 15:59:51 CST