During an import process I received the following error :
SSGDS001@eusadba1> imp dirdbo2/dirdbo2 full=y
Import: Release 220.127.116.11.0 - Production on Mon Sep 15 13:27:52 2003
Connected to: Oracle9i Enterprise Edition Release 18.104.22.168.0 - 64bit
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 22.214.171.124.0 - Production
Export file created by EXPORT:V09.02.00 via conventional path
Warning: the objects were exported by ROTEM2, not by you
import done in US7ASCII character set and AL16UTF16 NCHAR character set
import server uses WE8ISO8859P15 character set (possible charset
export client uses WE8MSWIN1252 character set (possible charset conversion)
export server uses UTF8 NCHAR character set (possible ncharset conversion)
Although the import ended succesfully (and the db up till now is functional), I would like to know whether this character set differences may pose a problem and if so, how do I remedy it ?
the messages are only warnings. But what they mean say is that the export was done using a different characterset than import. So, since there are possible characters in the first set which are not present in the second, character conversion will be done if possible. If not possible, import fails. Although the import ended succesfully and all functionality is available, it might be possible that some data will be different after the import.
It shows that you used the US7ASCII, which does not support all characters in Western Europe, especially things like special charcters on top of e or a etc.
To avoid this problem, check the character set useed by the database from whichthe export was takenand before importing change the NLS_LANG to that of the exported database. Like this