I have a couple of DBAs trying to transfer some data from a mainframe Oracle 9i database to a Unix 10g database.
The export is taken, setting no explicit NLS_LANG, as per Oracle recommendation and using the 9i Export utility.
The file is transferred using binary mode FTP to the Unix box, and Import from the 10g is used for the import, explicitly setting NLS_LANG to the target database setting.
The following error occurs:
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
With the Partitioning, Data Mining and Real Application Testing options
Export file created by EXPORT:V09.02.00 via direct path
Warning: the objects were exported by SYSTEM, not by you
import done in WE8ISO8859P1 character set and AL16UTF16 NCHAR character set
export client uses VN8MSWIN1258 character set (possible charset conversion)
IMP-00069: Could not convert to environment national character set's handle
IMP-00000: Import terminated unsuccessfully
Now, the source database is NOT in Vietnamese. If the database language is queried it says it is WE8ISO8859P1.
And yet the Import utility thinks it is Vietnamese!
The mainframe itself is set to English locale, obviously.
What can be going on here?
these may be clues or red herrings, but are observations...
The export is a complete export and is 148GB
If we take export of a small number of schemas, as we have recently, and we do it remotely (that is, connecting via a remote Unix 9i box ansd exporting directly to the 9i server, then transferring the dump to the 10g box) it loads just fine. We haven't been able to try the full export remotely because it impacts the mainframe server for many hours whereas the local export takes only a few hours (3ish).
Setting the Import to use the reported VN8MSWIN1258 character set still throws an error.
VN8MSWIN1258 looks like a Windows characterset. Where could a mainframe export pick this up?Can the client PC used to connect to Oracle affect anything?
Thanks for any help.