You would simply need to ensure that you have set Oracle to use a Unicode-compatible character encoding (I recommend UTF-8) and that no tool you are using to do the transfer is non-Unicode-safe.
You would simply need to ensure that you have set Oracle to use a Unicode-compatible character encoding (I recommend UTF-8) and that no tool you are using to do the transfer is non-Unicode-safe. Without knowing what you're using to do the transfer it's hard to give more specific information about where something is going wrong.
I think you mean UTF-16 as I'm sure chinese is like japanese and requires double byte characters to represent the full character set. – Dave Anderson Mar 8 '09 at 14:14 Dave, both UTF-8 and UTF-16 are multi-byte character encodings supporting the full Unicode repertoire. Both should be suitable.
– thomasrutter Mar 8 '09 at 15:10.
Make sure the database is setup with the correct character set to store/house chinese characters properly. If the database can't store it then it pointless to imported it. If the database can support the asian character set then set the client character set to a compatible one.
Once that is done the underline oci/odbc layer will handle the translation of one character set to the other as long as they are compatible.
Check the following. Database Character set (zhs16gbk) Set the local variable to NLS_LANG=SIMPLIFIED CHINESE. CHINA_UTF8 Open the excel file save the file to unicode text open the text file save the file to ANSI format In the PLSQL developer, we have option called text importer.
Using this tool we can import the data sucessfully.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.