| Import errors [message #425963] |
Tue, 13 October 2009 07:27  |
pleasehelp Messages: 20 Registered: January 2007 |
Junior Member |
|
|
Hi,
I just imported client's data into our database, but got several rows rejected during the import and several objects are invalid..
Export was done in 10.2.0.1, WE8MSWIN1252 character set and AL16UTF16 NCHAR character set..
Import was done in 10.2.0.4, WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
Is there a way to fix this issue just to import this data? I cannot change the character set because there are several other users using this database.. But is it possible to change the character set during the import session only?
Please help me..Thanks
|
|
|
| Re: Import errors [message #425968 is a reply to message #425963] |
Tue, 13 October 2009 07:46   |
Michel Cadot Messages: 29436 Registered: March 2007 Location: Nanterre, France, http://... |
Senior Member |
|
|
This is just an information message, in your case it does not matter as your target database character contains all characters of your source one and there was no conversion due to client setting.
Regards
Michel
|
|
|
| Re: Import errors [message #425970 is a reply to message #425963] |
Tue, 13 October 2009 07:49   |
pleasehelp Messages: 20 Registered: January 2007 |
Junior Member |
|
|
Thanks Michel..
But then I've been getting several of these errors:
IMP-00019: row rejected due to ORACLE error 12899
IMP-00003: ORACLE error 12899 encountered
ORA-12899: value too large for column
Isnt it due to the character set difference? Target database being Unicode?
THanks
|
|
|
| Re: Import errors [message #425978 is a reply to message #425970] |
Tue, 13 October 2009 08:40   |
Michel Cadot Messages: 29436 Registered: March 2007 Location: Nanterre, France, http://... |
Senior Member |
|
|
This is another point.
AL32UTF8 is a variable length character set, each character can be on 1 to 3 bytes.
You have to either:
- change the definition of each (var)char columns from a byte one to a char one
- enlarge all fields that may contain characters that are not in 0-127 code points.
Regards
Michel
|
|
|
| Re: Import errors [message #426244 is a reply to message #425963] |
Wed, 14 October 2009 09:57   |
pleasehelp Messages: 20 Registered: January 2007 |
Junior Member |
|
|
Thanks Michel.
Can this issue be resolved if use Data pump export and import?
Will it work fine if I use data pump export and import to unicode database?
Thanks
|
|
|
| Re: Import errors [message #426249 is a reply to message #426244] |
Wed, 14 October 2009 10:09   |
Michel Cadot Messages: 29436 Registered: March 2007 Location: Nanterre, France, http://... |
Senior Member |
|
|
The issue is independent of the tool you will it is inherent of the data.
You ONLY have the 2 options I mentioned. Oh Yes, you have a third one: don't import the offended data.
Regards
Michel
|
|
|
|
|
| Re: Import errors [message #426471 is a reply to message #426264] |
Thu, 15 October 2009 10:27   |
pleasehelp Messages: 20 Registered: January 2007 |
Junior Member |
|
|
Oh ok.
CSSCAN - is it like a command before I run the import into unicode database? Will it convert the data by itself?
Thanks much
|
|
|
| Re: Import errors [message #426472 is a reply to message #426471] |
Thu, 15 October 2009 10:40   |
Michel Cadot Messages: 29436 Registered: March 2007 Location: Nanterre, France, http://... |
Senior Member |
|
|
No, csscan just verifies where there can be a problem when (for example) you import from a character set to another one.
In your case, you already know where is the problem as you already got the error.
Regards
Michel
|
|
|
|