PL/SQL database character set(AL32UTF8) and Client character set(ZHS16GBK) are different

啓動PL/SQL Developer 報字符編碼不一致錯誤

Database character set (AL32UTF8) and Client character set (ZHS16GBK) are different.
Character set conversion may cause unexpected results.

Note: you can set the client character set through the NLS_LANG environment variable or the NLS_LANG registry key in
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_Oracle_10g.

打開註冊表,經過命令regedit。找到到文中提示的路徑，發現NLS_LANG鍵的值爲:

SIMPLIFIED CHINESE_CHINA.ZHS16GBK

修改成：SIMPLIFIED CHINESE_CHINA.AL32UTF8便可

 

還有一種多是因爲安裝11g的時候沒選擇自定義安裝形成的

Database character set (AL32UTF8) and Client character set (ZHS16GBK) are different.
Character set conversion may cause unexpected results.
Note: you can set the client character set through the NLS_LANG environment variable or the NLS_LANG registry key in
HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/KEY_OraDb11g_home

SIMPLIFIED CHINESE_CHINA.ZHS16GBK 包含 AMERICAN_AMERICA.AL32UTF8.
這但是個麻煩事，不是改客戶端字符集的問題。要改數據庫的字符集：
SQL> conn /as sysdba
SQL> shutdown immediate;
SQL> startup mount
SQL> ALTER SYSTEM ENABLE RESTRICTED SESSION;
SQL> ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
SQL> ALTER SYSTEM SET AQ_TM_PROCESSES=0;
SQL> alter database open;
SQL> ALTER DATABASE CHARACTER SET ZHS16GBK;
ORA-12712: new character set must be a superset of old character set
提示咱們的字符集：新字符集必須爲舊字符集的超集，這時咱們能夠跳過超集的檢查作更改：
SQL> ALTER DATABASE character set INTERNAL_USE ZHS16GBK;
--咱們看到這個過程和以前ALTER DATABASE CHARACTER SET操做的內部過程是徹底相同的，也就是說INTERNAL_USE提供的幫助就是使Oracle數據庫繞過了子集與超集的校驗.
SQL> select * from v$nls_parameters; 
SQL> shutdown immediate;
SQL> startup
SQL> select * from v$nls_parameters;
之後安裝oracle11g的時候記得選擇自定義安裝，把這個字符集的事情事先弄好