Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Export/Import and NLS

Re: Export/Import and NLS

From: <mikelsharp_at_my-dejanews.com>
Date: Thu, 04 Mar 1999 01:45:37 GMT
Message-ID: <7bkojv$88l$1@nnrp1.dejanews.com>


Thanks Mike! I tried it and it seems to work. Like you, I had to write a quick C program that opens the dump file, lseeks to the 3rd byte, and writes '0x1f' value to that byte.

One alternate, "unsupported" way I found out from Oracle support is to actually change the charset of the source database, which involves modifying the source database's data dictionary. I've tried that on a test database and it worked as well, but obviously much less preferrable than binary-editting the export file.

Anyway, thanks again (and let's all live dangerously!)

Pei

In article <3_WA2.62006$qw3.3908295_at_nnrp1.tor.metronet.ca>,   "Mike Merrett" <merrettmi_at_rmoc.on.ca> wrote:
> Here is the "unsupported" answer I got from oracle on getting us7ascii
> export into a we8iso8859p1 database (they gave 3 things to try - here is the
> one that did actually work)
>
> - export the us7ascii database
> - using a binary editor change the third byte of the export(.dmp) file from
> 0x01 to 0x1f
>
> -import into the we8iso8859p1
>
> (I had to write a quick gcc program to do this because of the file sizes)
>
> Hope this helps.
> Mike Merrett
>
> Pei L. Ku wrote in message <7aphj2$40h$1_at_news-1.news.gte.net>...
> >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
> >
> >
>
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Wed Mar 03 1999 - 19:45:37 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US