"Server uses WE8MSWIN1252 character set (possible charset conversion)" pertains to the database character set of the source database so you cannot do anything about it, I guess, unless you have control over that database. If you are sure the source database contained Arabic data, then this data was stored incorrectly labeled as Western European, using pass-through configuration. If I remember correctly, Export 188.8.131.52 stores the dump file content in the source DB character set and not in the export NLS_LANG character set (Export done in AR8MSWIN1256). This would allow the data to be rescued. However, if I am mistaken and the export data is still stored in the NLS_LANG character set (like it used to be in older releases), then the Export already corrupted the data by converting it from WE8MSWIN1252 to AR8MSWIN1256 and nothing can be done.
To rescue the data you need to:
1. Create an empty temporary database with WE8MSWIN1252 character set.
2. Import the dump file into this database, setting NLS_LANG=.WE8MSWIN1252.
3. Change the database character set of the temporary database to AR8MSWIN1256 (assuming the original data is in AR8MSWIN1256 and not, for example, AR8ISO8859P6). This is achieved with csscan utility and csalter.plb script. There are MOS notes describing this process.
4. Move the data from the temporary database to the target database with Data Pump.
I am afraid there is no simpler way.
Thanks for the very helpful reply.
I'll perform those steps and get back to you.
Can you please log on to the database by SQLPLUS, if the character set in Arabic you will find the SQLPLUS log on screen in Arabic (this is from windows machine).
make sure that the Arabic key-board is installed, then from the regedit serch for NLS_LANG and change all the found values to AMERICAN_AMERICA.AR8MSWIN1256, then test any select from sqqlus or SQL-Developer.
I hope this help.
The first few sentences states...
"" the issue is that the data has arabic characters that are appearing as ?? .the following is from the log file that came with the .dmp file: ""
Implies.. concerns with export using exp..
Ensure the appropriate CHAR & NCHAR settings at the Source. Advice, to re-take the export using expdp and validate again the export logfile.
Thanks and Regards
Oracle Database Architect
Riyadh - Kingdom of Saudi Arabia