RE: import fails due to different character set

Raghu,  

Have a look at the error message - it is "value too large for column". UTF8 is a mult-byte characterset while the older WE8..P1 is a single byte characterset. In the LEGAL_LAST_NAME column, you have one or more rows which has at least one or more special characters which expands from the WE8 single byte entry to occupy a UTF8 double (or multi-byte) entry. You will have to expand the LEGAL_LAST_NAME column to accomodate this expansion.  

And while you are it, you might as well expand those other columns which may possibly hold special characters. This is especially true for Name columns...  

Hth,
John Kanagaraj <><
DB Soft Inc
Phone: 408-970-7002 (W)  

Co-Author: Oracle Database 10g Insider Solutions http://www.amazon.com/exec/obidos/tg/detail/-/0672327910/  

• The opinions and facts contained in this message are entirely mine and do not reflect those of my employer or customers **

  ---

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Kota, Raghu Sent: Wednesday, February 08, 2006 2:31 PM To: oracle-l_at_freelists.org
Subject: import fails due to different character set  

Hi Guys,  

Could any body suggest workaround to import data from database charset WE8ISO8859P1 to database charset UTF8, Here it is my error!  

import server uses UTF8 character set (possible charset conversion)

export client uses WE8ISO8859P1 character set (possible charset conversion)

. importing RAMSTG's objects into RAMSTG

. . . importing table "CLASS_REC"

IMP-00019: row rejected due to ORACLE error 12899

IMP-00003: ORACLE error 12899 encountered

ORA-12899: value too large for column
"RAMSTG"."CLASS_REC"."LEGAL_LAST_NAME" (actual: 22, maximum: 20)

Column : 1051003  

Thanks

Raghu.  

--
http://www.freelists.org/webpage/oracle-l