将数据库启动到RESTRICTED模式下做字符集更改:
cmd
1. SQL> conn /as sysdba
2. Connected.
3. SQL> shutdown immediate;
4. Database closed.
5. Database dismounted.
6. ORACLE instance shut down.
7. SQL> startup mount
8. ORACLE instance started.
9. Total System Global Area 236000356 bytes
10. Fixed Size 451684 bytes
11. Variable Size 201326592 bytes
12. Database Buffers 33554432 bytes
13. Redo Buffers 667648 bytes
14. Database mounted.
15. SQL> ALTER SYSTEM ENABLE RESTRICTED SESSION;
16. System altered.
17. SQL> ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
18. System altered.
19. SQL> ALTER SYSTEM SET AQ_TM_PROCESSES=0;
20. System altered.
21. SQL> alter database open;
22. Database altered.
23. SQL> ALTER DATABASE CHARACTER SET ZHS16GBK;
24. ALTER DATABASE CHARACTER SET ZHS16GBK
25. ERROR at line 1:
26. ORA-12712: new character set must be a superset of old character set
提示我们的字符集:新字符集必须为旧字符集的超集,这时我们可以跳过超集的检查做更改:
1. SQL> ALTER DATABASE character set INTERNAL_USE ZHS16GBK;
2. Database altered.
3. SQL> select * from v$nls_parameters;
4. 略
5. 19 rows selected.
重启检查是否更改完成:
1. SQL> shutdown immediate;
2. Database closed.
3. Database dismounted.
4. ORACLE instance shut down.
5. SQL> startup
6. ORACLE instance started.
7. Total System Global Area 236000356 bytes
8. Fixed Size 451684 bytes
9. Variable Size 201326592 bytes
10. Database Buffers 33554432 bytes
11. Redo Buffers 667648 bytes
12. Database mounted.
13. Database opened.
14. SQL> select * from v$nls_parameters;
15. 略
16. 19 rows selected.
我们看到这个过程和之前ALTER DATABASE CHARACTER SET操作的内部过程是完全相同的,也就是说INTERNAL_USE提供的帮助就是使Oracle数据库绕过了子集与超集的校验.
这一方法在某些方面是有用处的,比如测试;应用于产品环境大家应该格外小心,除了你以外,没有人会为此带来的后果负责。
结语(我们不妨再说一次):
对于DBA来说,有一个很重要的原则就是:不要把你的数据库置于危险的境地!
这就要求我们,在进行任何可能对