This content has been marked as final. Show 3 replies
Source database version is 10.2.0.3.0 and I can't give exact expdp command because I recived that file and have no acces to that server. Target databse version is 220.127.116.11.0 ja impdp command:
impdp xxx@yyy directory=datapump dumpfile=filename.dmp remap_tablespace=xxx:yyy remap_tablespace=xxx:zzz logfile=impdp.log
+## Does it mean that already in source systems those names were not correctly stored or did impdp messed things up? What are the options to correct the situation?+
The impdp messed things up because characters were stored incorrectly in the source database. The characters you listed (š/ž) are WE8MSWIN1252 characters by not WE8DEC characters. They were stored in the source database thanks to a pass-through (garbage-in/garbage-out) configuration.
The replacement character you are talking about is the default Unicode replacement character U+FFFD, which encoded in UTF-8 (AL32UTF8) is 0xEF 0xBF 0xBD, i.e. CHR(15712189).
Your options are:
1) Correct the names manually, or
a) Delete the incorrect rows,
b) Create a small temporary database with WE8DEC database character set,
c) Import the problematic tables from your export file into this database
d) Run Character Set Scanner utility on the temporary database:
csscan full=y fromchar=we8mswin1252 tochar=we8mswin1252
Hopefully, only changeless data will be reported in scan.txt
e) Run the following in SQL*Plus as SYSDBA -- you must be the only logged session
SQL> ALTER SYSTEM ENABLE RESTRICTED SESSION;
f) Restart the database
g) Re-export the problematic tables
h) Import the new export file into the target AL32UTF8 database. This time the names should be fine.
i) Drop the temporary database.