expdp 报 39014 39029 31671 600
朋友们好 客户要求用ZHS32GB18030 的字符集 ，新换操作系统为SUSE12，源库为 11.2.0.4.0，目标库为12.1.0.2.0，由于11R2里不含ZHS32GB18030的字符集，所以先手工建库指定ZHS32GB18030，然后升级为12R1，这个都正常，但在12R1做expdp实验时，报以下错误，GOOGLE与MOS查均无结果，但其它正常字符集的11R2升12R1，做此实验正常，不知是否一定是GB18030字符集的原因导致，如果更换超集字符集，那应该更换哪个？谢谢oracle@suse:~> expdp scott/tiger directory=testbak dumpfile=test12cdept.dmp logfile=test12cdept.log tables=dept
Export: Release 12.1.0.2.0 - Production on Wed Nov 16 07:28:55 2016
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
Starting "SCOTT"."SYS_EXPORT_TABLE_02": scott/******** directory=testbak dumpfile=test12cdept.dmp logfile=test12cdept.log tables=dept
Estimate in progress using BLOCKS method...
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW00" prematurely terminated
ORA-31671: Worker process DW00 had an unhandled exception.
ORA-00600: internal error code, arguments: , [], [], [], [], [], [], [], [], [], [], []
Estimate in progress using BLOCKS method...
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 2 with process name "DW00" prematurely terminated
ORA-31671: Worker process DW00 had an unhandled exception.
ORA-00600: internal error code, arguments: , [], [], [], [], [], [], [], [], [], [], []
Job "SCOTT"."SYS_EXPORT_TABLE_02" stopped due to fatal error at Wed Nov 16 07:29:59 2016 elapsed 0 00:01:04
oracle@suse:~> echo $LD_LIBRARY_PATH
/u01/app/oracle/product/12.1.0/db_1/lib Does Oracle RDBMS supports the GB18030 encoding / characterset ?
Oracle RDBMS supports the GB18030-2000 standard trough the ZHS32GB18030 and the AL32UTF8 or UTF8 Character Set.
Oracle fully supports GB18030-2000 non-Unicode input/output using the ZHS32GB18030 Client-Only Character Set .
Note that the ZHS32GB18030 Character Set is a Client-Only Character Set, http://download.oracle.com/docs/cd/E11882_01/server.112/e10729/applocaledata.htm#NLSPG588
Hence it is not supported to use ZHS32GB18030 as NLS_CHARACTERSET. If your database uses ZHS32GB18030 as NLS_CHARACTERSET then we strongly recommend to migrate as soon as possible to AL32UTF8. 不过在11.2中UTF8同样是不推荐的字符集之一，那么如果需要在客户端使用GB18030编码，那么推荐使用AL32UTF8字符集。如果客户端使用GB18030-2000编码，那么可以在数据库中选择AL32UTF8字符集，而客户端字符集选择ZHS32GB18030，所有的客户端字符都可以顺利的保存到服务器端或从服务器端读取。如果客户端选择GB18030-2005编码，那么没有专门的客户端字符集与之对应，因此客户端应该与数据库保持一致，都选择AL32UTF8字符集。
http://yangtingkun.net/?p=47
页:
[1]