Oracle11g changed the character set AL32UTF8 to ZHS16GBK

Oracle11g changed the character set AL32UTF8 to ZHS16GBK SQL code 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_home1. SIMPLIFIED CHINESE_CHINA.ZHS16GBK contains AMERICAN_AMERI CA. AL32UTF8. -- this is a headache, not the problem of changing the client character set. The character set of the database to be modified. 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 -- prompt our character set: the new character set must be a superset of the old character set. In this case, we can skip the superset check and make changes: SQL> ALTER DATABASE c Haracter set INTERNAL_USE ZHS16GBK; -- we can see that this process is exactly the same as the internal process of the previously alter database character set operation, that is to say, INTERNAL_USE helps the Oracle database bypass the validation of the subset and superset. SQL> select * from v $ nls_parameters; SQL> shutdown immediate; SQL> startup SQL> select * from v $ nls_parameters; -- Remember to select Custom installation when installing oracle11g in the future, get this character set in advance.