Re: Characters losts during Import (8.1.6) -> (9.2.0.6)

Guitarator wrote:
> Hi
> sorry to come back again. I must to do Export one on my data schema
> from my 8.1.6 server to another 9.2.0.6. What is the best way ?
>
> 1) First test: I does my export => i've a kabalistic character after
> Import on my 9.2.0.6
>
> 2) Seconc test: Setting the NLS_LANG in environement to .WE8ISO8859P1
> before my Export => on import in 9.2.0.6 I've the same problem.
>
> 3) Third test: I don't know. Migrate the database in another Charcater
> Set ?
>
> 8.1.6 NLS Parameters
> NLS_LANGUAGE = FRENCH
> NLS_TERRITORY = FRANCE
> NLS_CHARACTERSET = US7ASCII
> NLS_SORT = FRENCH
> NLS_NCHAR_CHARACTERSET = US7ASCII
>
> 9.2.0.6 NLS Parameters
> NLS_LANGUAGE = FRENCH
> NLS_TERRITORY = FRANCE
> NLS_CHARACTERSET = WE8ISO8859P1
> NLS_SORT = FRENCH
> NLS_NCHAR_CHARACTERSET = AL16UTF16
>
> Thanks you very much for all welcome answers
> Denis

Please see Note:158577.1 on metalink, and see http://asktom.oracle.com/~tkyte/flat/index.html

Your problem is there are several places a conversion is possible, and it is difficult to set everything up to fool oracle into not converting in all the places (see
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:497221737858 ).

Your #2 shouldn't work because the export would be converting from 7 bit to 8 bit, losing the high bit. #1 wouldn't work because you'd be converting 7 bit to 8 bit on import, losing the high bit. There are strange things you can do to fool oracle internally, but better to do the understandable thing - flat files. Alternatively, if there is only one French character that gets messed up in a limited number of tables, maybe you can update that one character after the import.

jg

-- 
@home.com is bogus.
http://www.rotten.com/today/