Re: Export / Import and CharacterSets

Hi !

using the US7ASCII scheme for storing 8bit-data DID work without any problems
in ORACLE releases before 7.2
After that, they obviously applied the 7bit limit a little more strictly, hence
your problems. To be precise: there is NO valid translation for Umlauts in the
WE8ISO8859P1 space to US7ASCII.

But hope is ahead (I had this problem before ;-) ): * export your valued data (NLS_LANG=American_America.US7ASCII) * patch the third byte in your exportfile by replacing the third byte 0x01

    with the value 0x1f
* import to your production database with NLS_LANG=American_America.WE8IS8859P1

I assumed that in fact you used ISO8859-character set to store our wonderful Umlauts, hence
the "0x1f" value

Not documented, but for me it worked...

Hope this helps

Frank

Rolf Hauck schrieb in Nachricht <360A316D.D51F99F9_at_datenrevision.de>...
>Hi,
>I'm trying to transport character data from our develepment database to
>production database, and I'm losing all my German characters. The
>development system is set up with NLS_LANG=AMERICAN_AMERICA.US7ASCII
>(Oracle 7.3.2.3). The production system uses
>AMERICAN_AMERICA.WE8ISO8859P1 (Oracle 7.3.4).
>I can't make exp/imp behave like it's documented:
>
>From Ora 7 Server Utilities Guide:
>The export file identifies the character encoding scheme used for the
>character data in the file. If that character set is any single-byte
>character set (for example, EBCDIC or USASCII7), and if the character
>set used by the target database is also a single-byte character set,
>then the data is automatically converted to the character encoding
>scheme specified for the user session during import, as specified by the
>NLS_LANG parameter. After the data has been converted to the session
>character set, it is then converted to the database character set.
>
>What am I missing?
>
>TIA Rolf
Received on Thu Sep 24 1998 - 08:45:35 CDT