Error message displayed in PLSQL Developer is garbled, plsqldeveloper
Error messages in PLSQL Developer are garbled
Connection environment: win 7
Database Version: oracle 11g
Simulate an error and view the error prompt to display "???" The garbled problem is as follows:
Check:
1. V $ NLS_PARAMETERS
To display CHINESE characters, NLS_LANGUAGE should be simplified chinese.
2. Enter the Registry to view the language
Find "run" in the "Start" menu of the computer, and enter "regedit" in the dialog box to open the computer registry. Choose HKEY_LOCAL_MACHINE ---> SOFTWARE ---> ORACLE ---> KEY_OraDb11g_home1, locate NLS_LANG, and check whether the value is: SIMPLIFIED CHINESE_CHINA.ZHS16GBK.
3. Set environment variables in the system
Variable name: NLS_LANG
Variable value: SIMPLIFIED CHINESE_CHINA.ZHS16GBK
Log out of PLSQL Developer and log on again
Run the simulation again to report an error. The error prompt is displayed in Chinese.
**************************************** *******Statement************************************************
Original works, from "Deep Blue blog" blog, welcome to reprint, reprint please be sure to indicate the source (http://blog.csdn.net/huangyanlong ).
Please leave a message if the statement is incorrect. Thank you very much.
Reminder: Click the directory to view the directory.
*****************************************************************************************************
Plsql developer garbled
Find the following solutions elsewhere:
1. Set the key value of HKEY_LOCAL_MACHINE-> SOFTWERE-> ORACLE-> HOME0-> NLS_LANG in the Registry to Japan. In addition, all fonts under Tools> Preferences> font of Plsql developer are changed to Japanese.
I don't know whether to use it or not. I have never used a Japanese system ~~
The Chinese data entered by plsql developer becomes garbled
If you don't understand what you mean, you can see that your graph is an insert statement, which means that you are garbled before the insert statement. Do you first write the insert statement in the win editor and paste it into unix? If this is the case, you should use ftp to send this script.