Re: Import/Export problem

In article <01bd8374$045b9e00$ab652ca6_at_none.mcit.com>, "Slava Krivonos" wrote:

Two considerations,

If you get the NLS_CHARACTERS wrong, when you try to restart your database it will not open, and you will never be able to open it again. So, BACKUP FIRST!!!

Secondly, I would recommend character set WE8ISO8859P1 or WE8ISO8859P9 as they are generic ISO sets and cover most cases. WE8DEC is similar but has a DEC slant to it.

regs

Neil Chandler

>UPDATE SYS.PROPS$ set value='WE8DEC' where name='NLS_CHARACTERSET';
>
>You may be need to add 8th bit code table support before by Oracle
>Installer without tuching DB.
>
>You will get 8th bit DB.
>
>Steven Teo <teobc_at_hpsgmx18.sgp.hp.com> wrote in article
><355C560A.3259F88F_at_hpsgmx18.sgp.hp.com>...
>> Hi,
>> What about CHAR_SET, NLS issues? We have a database with CHAR_SET or
>> NLS_LANG set to US7-ASCII... however, there are 8-bit characters stored
>> in the database. As a side effect, it works. Now, we are trying to
>> export the data and import it into an 8-bit Char_SET, and translation
>> occurs, and the 8th bit is lost.. resulting in data lost... any way to
>> get around this?
>>
>> I was thinking exporting the data in US_7ASCII to a dmp file.. and
>> then modify the DMP file to the 8-bit char set before importing... ??
>>
>> Steve
>>
>>
>>
>>
Received on Wed May 20 1998 - 00:00:00 CDT